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

Thierry Parmentelat thierry.parmentelat at inria.fr
Wed Feb 13 12:41:52 PST 2013

On Feb 13, 2013, at 9:26 PM, Thierry Parmentelat wrote:

> Right now I'm using 
> systemd.log_level=debug systemd.log_target=kmsg

OK,  of course, I should use log_target=console

Which I just did, and that shows a brief mention to pl_sysinit:
About to execute /etc/init.d/pl_sysinit^M
Forked /etc/init.d/pl_sysinit as 127^M
but that's it

none of my own output shows up on the console; is there a way that I can see that again ?
or did anyone decide the console is now private property or something ;)

seriously, there has to be a way for us to debug our own initscripts, what am I missing here ?

Thanks -- Thierry

More information about the systemd-devel mailing list