[systemd-devel] troubleshooting different behaviour of systemd between f16 and f18

Thierry Parmentelat thierry.parmentelat at inria.fr
Wed Feb 13 12:26:58 PST 2013

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 ;)
Any means to restore a behaviour where most would get dumped on the terminal ?
Right now I'm using 
systemd.log_level=debug systemd.log_target=kmsg

and btw what does this line here mean ?
[    6.457686] systemd-journald[66]: Received SIGUSR1

Thanks ! -- Thierry

More information about the systemd-devel mailing list