Am 14.04.2013 07:33, schrieb Andrey Borzenkov:
В Sun, 14 Apr 2013 01:34:53 +0200 Stefan Seyfried <stefan.seyfried@googlemail.com> пишет:
That's not feasible as I need to enable debugging at boot and then have lots debug information wasting cycles just to debug the shutdown 2 weeks later once a new kernel is out. Or is there a way to enable debugging just before shutdown? I have not found one.
SIGRTMIN+22, SIGRTMIN+23 Sets the log level to debug (or info on SIGRTMIN+23), as controlled via systemd.log_level=debug (or systemd.log_level=info on SIGRTMIN+23) on the kernel command line.
SIGRTMIN+26, SIGRTMIN+27, SIGRTMIN+28, SIGRTMIN+29 Sets the log level to journal-or-kmsg (or console on SIGRTMIN+27,
You can list signals using "kill -l"; SIGRTMIN+22 is 56 here and SIGRTMIN+27 is 61. So
kill -56 1 kill -61 1 dmesg -n 7
That's good to know. I would put this into before.local so that I don't forget it, but I'm pretty sure (have not tried) that this no longer works with systemd. Thanks, this might help when the next kernel comes out. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org