[FS#4225] logread starts before interface is up

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Thu Jan 13 07:53:04 PST 2022


The following task has a new comment added:

FS#4225 - logread starts before interface is up
User who did this - Harry Martin (systemdlete)

I tried changing the order of the init scripts by moving the "log" service from 12th to 21st in the sequence so that it would come just after "network" service.  This does not work either and may actually be losing even more information.

At first it may seem like the question of "which came first, the chicken or the egg?"  But I think it is more that the chicken and the egg need to be separated.  The "log" service launches both the system log daemon (which saves early boot messages in its ring buffer) and the logread daemon which forwards the messages on to the syslog server.

Instead, if the logd daemon were launched separately, early on in the boot process, and the logread daemon were launched later on after the "network" service has completed its startup, hopefully fewer messages would be dropped or lost.  In fact, with a sufficient ring buffer size, lost messages might be virtually eliminated.

More information can be found at the following URL:

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

More information about the openwrt-bugs mailing list