[systemd-devel] troubleshooting different behaviour of systemd between f16 and f18
lennart at poettering.net
Wed Feb 13 13:29:13 PST 2013
On Wed, 13.02.13 21:26, Thierry Parmentelat (thierry.parmentelat at inria.fr) wrote:
> On Feb 13, 2013, at 4:41 PM, Lennart Poettering wrote:
> > Log output of services ends up in the journal these days, from both
> > early boot and late boot. And used to end up in syslog, except for
> > early-boot where it ended up in kmsg -- which is probably what you saw.
> > hence, check syslog or journalctl.
> Thanks for the suggestion, but given that the network does not start
> this is not going to work ;)
Hmm? Why does syslog/journalctl require the network?
> Any means to restore a behaviour where most would get dumped on the
> terminal ?
Well, note that old systemd versions only wrote earl-yboot stuff to
kmsg, nothing else.
With newer systemd you can pass systemd.journald.forward_to_kmsg=1 or
systemd.journald.forward_to_console=1 on the kernel command line to get
*all* logs spewed into kmsg/console. (Note that this will slow thins
down drastically, hence is useful only for debugging purposes...)
> Right now I'm using
> systemd.log_level=debug systemd.log_target=kmsg
With that you control only systemd's own output.
> and btw what does this line here mean ?
> [ 6.457686] systemd-journald: Received SIGUSR1
When journald shall flush its logs into /var then SIGUSR1 is sent to it
as notification for that. journald usually starts before /var is
available and writable, hence it will buffer logs in /run during that
time, until it gets notified to flush things to /var.
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel