FS#41942 - [systemd] events missing from journal when using quiet on kernel commandline
Attached to Project:
Arch Linux
Opened by Tarqi Kazan (Tarqi) - Thursday, 11 September 2014, 22:59 GMT
Last edited by Dave Reisner (falconindy) - Friday, 12 September 2014, 23:48 GMT
Opened by Tarqi Kazan (Tarqi) - Thursday, 11 September 2014, 22:59 GMT
Last edited by Dave Reisner (falconindy) - Friday, 12 September 2014, 23:48 GMT
|
Details
Description:
systemd events missing from journal when using quiet on kernel commandline When the word "quiet" is used on the kernel commandline, systemd will not log some actions like this: ... systemd[1]: Starting foo service... ... systemd[1]: Started foo service. ... systemd[1]: Stopping foo service... ... systemd[1]: Stopped foo service. This will not happen, if "quiet" has been removed from the kernel commandline, so everything is logged like it should. Additional info: * systemd 216-3 * linux 3.16.1-1 * See BBS: https://bbs.archlinux.org/viewtopic.php?id=186623 Steps to reproduce: * Boot with "quiet" on the kernel commandline * start/stop a service * check the journal * repeat without "quiet" on the kernel commandline |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 12 September 2014, 23:48 GMT
Reason for closing: Not a bug
Additional comments about closing: Working as intended -- as of v215, passing systemd.log_level=info is also needed.
Friday, 12 September 2014, 23:48 GMT
Reason for closing: Not a bug
Additional comments about closing: Working as intended -- as of v215, passing systemd.log_level=info is also needed.
http://cgit.freedesktop.org/systemd/systemd/tree/src/core/main.c#n365
I suspect that you can get what you want if you add "systemd.log_level=info" to your kernel commandline. Make sure it's after "quiet".
> I like systemd, but it's not easy to stay on track...
You're not alone in this sentiment.