Bug#826297: offer a shutdowm logging service

積丹尼 Dan Jacobson jidanni at jidanni.org
Tue Jun 7 15:09:59 BST 2016


>>>>> "MB" == Michael Biebl <biebl at debian.org> writes:

MB> The upstream documentation assumes you have a merged-usr setup.
MB> If you change the paths to use /lib instead of /usr/lib (i.e.
MB> /lib/systemd/system-shutdown/debug.sh), it should work. Can you confirm?

OK indeed it does. (However there seem to be some doubled messages, and
the verbosity overfills the file a bit. probably due to the kernel parameters.)

>> 2. Offer it as a convenient service that one can just enable / disable.

MB> I guess this won't work. This debugging mechanism doesn't use service
MB> files. I don't see how we could put this into a service unit.

Well it is too bad the user needs to deposit in that directory instead
of doing some command...

Anyways surely mentioning this method in
/usr/share/doc/systemd/README.Debian.gz "Debugging
boot/shutdown problems" would be valuable.

>> By the way, it would be great if boot logs could also be kept in such a
>> fashion too.

MB> You can use the journal, which contains that information.

Indeed it _seems_ nowadays everything one sees during boot (after the grub
countdown) does end up in journalctl and dmesg... so no more need for
bootlogd, etc.




More information about the Pkg-systemd-maintainers mailing list