Bug#762700: systemd: journald fails to forward most boot messages to syslog

Raphaël Halimi raphael.halimi at gmail.com
Wed Feb 25 22:52:57 GMT 2015

Le 25/02/2015 22:18, Christian Seiler a écrit :
> Now this was really extreme, but there is software out there that
> does log heavily (also depending on the log level set by the admin),
> and just having a queue of 11 is really, really short in such
> situations. Yes, at some point there has to be a cutoff, but I
> don't think it should be 11.

Indeed, it doesn't happen only during boot, and you don't need to spam
the syslog to lose messages. I originally noticed the problem with
NetworkManager; I simply clicked in the applet on an already connected
Ethernet device to make it quickly reconnect (I was testing a change in
my DHCP server config, hence the syslog watching). NetworkManager's
regular output for a disconnection immediately followed by a connection
is often enough to lose some messages (but not always, it maybe
dependent on the DHCP server's responsiveness in this case).

Raphaël Halimi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150225/b505da26/attachment-0002.sig>

More information about the Pkg-systemd-maintainers mailing list