Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes two long-standing issues with logread: #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

icegood
Copy link

@icegood icegood commented Jan 1, 2024

  1. async reconnect for logd
  2. be able to send logs to different targets in one process. The latter will allow to remove ugly stuff in startup script where two copies of logread might be started

Check for related pr for this (in near future).

1) async reconnect for logd
2) be able to send logs to different targets in one process.
The latter will allow to remove ugly stuff in startup script
where two copies of logread might be started

Check for related pr for this.

Signed-off-by: Serhii Ivanov <icegood1980@gmail.com>
@blogic
Copy link
Contributor

blogic commented Jan 1, 2024

437 line diffstat and 4 lines explaining what they do, that is 2 orders of magnitude

@ynezz
Copy link
Member

ynezz commented Jan 2, 2024

437 line diffstat and 4 lines explaining what they do, that is 2 orders of magnitude

In other words, you should split this into (multiple) separate commits and add more details in the commit descriptions

icegood added a commit to icegood/openwrt that referenced this pull request Jan 2, 2024
It will make logger more consistent to other ones plus one process
will reduce consuption of memory

2) Get rid of mixed log_size parameter. Instead, two separated
log_max_file_size (for maximal file size in case of logging in file)
and log_buffer_size (for memory size in logd)
are introduced.

Therefore, user will not guess anymore, what actually log_size did.

Dependencies:
openwrt/ubox#2

Signed-off-by: Serhii Ivanov <icegood1980@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants