Hoiw to keep systemd quiet?

karol · 2014-07-23 16:09:18

I have 'quiet' on the kernel command line, but once in a while after fscking my drive systemd will print to the console. No warnings / errors, just the usual stuff like http://www.freedesktop.org/wiki/Software/systemd/
A separate and less irritating issue is that something is printing output on reboot / shutdown.

There are a few reports about this, but they have been closed as 'upstream'. Does anyone know how to fix this?
I'm using syslinux, I boot to the tty and run 'startx' from there to get X with dwm.

stevenhoneyman · 2014-07-23 16:49:43

Remove it

On a slightly more serious note, try:

quiet systemd.show_status=0

on kernel command line.
There's a horribly irritating crypttab/systemd-ask-passwrod bug they still havent fixed, and that's the workaround that shut it up for me

cafe · 2014-07-24 12:33:07

File System Check (fsck) messages do not come from systemd, but you can filter them out..
This was already discussed in this previous thread.

I don't like the standard behavior of fsck either..
I would rather have only error messages in stderr, instead of info messages saying that my drive is clean..
If it is clean, it is clean.. good to go!

The shutdown process it definitely not quiet, even with the "quiet" kernel boot parameter.
I'm afraid we need a patch to make it 100% clean..

Cheers,

karol · 2014-07-24 12:46:06

I don't care about the fsck messages themselves, but after the fsck, instead of getting just a prompt so I can log it, systemd prints a bunch of stuff first, similar to the picture on the right: http://www.freedesktop.org/wiki/Software/systemd/
Only part of the boot messages get printed, half of them seem to obey the 'quiet' parameter and then systemd decides it wants to show me who's boss.

karol · 2014-07-24 13:31:10

I re-read th man page and found

systemd.show_status=
           Takes a boolean argument or the constant auto. If true, shows terse service status updates on the
           console during bootup.  auto behaves like false until a service fails or there is a significant delay
           in boot. Defaults to true, unless quiet is passed as kernel command line option in which case it
           defaults to auto.

I guess the fsck counts as 'a significant delay in boot' - that's why I was getting these messages.

cafe · 2014-07-24 15:24:33

I see..
So, systemd.show_status=false is lighter than the quiet kernel boot parameter.

Maybe we have to look case by case..
In my machine, those "[OK] messages" disappear with the "quiet" kernel boot parameter,

Here's some good information on the subject : Silent Boot
I think the login information about the distro and kernel version are part of getty.. "/etc/issue", and "/etc/motd" can be tuned as well.

So, what exactly is shown in your boot?

karol · 2014-07-24 15:41:21

The problem is that these messages appear after the partition is fscked.
I did read that wiki article. I guess I have to use 'systemd.show_status=0' to keep systemd from printing stuff I don't need.

cafe · 2014-07-25 00:59:31

During the boot process there are two places where fsck can be called.
* The first is in the initramfs image : It will call fsck on the root partition if you have it configured on /etc/mkinitcpio.conf in the HOOKS section.
* The second one is called by systemd during normal boot.
You can get rid of the second message, but not the first.. Removing the first is absolutely not recommended at all.

Good luck in your quest, and please give us some feedback if you manage to get rid of shutdown messages ;-D

karol · 2014-07-25 01:14:19

I am not talking about the fsck messages, but the ones that follow.

cafe · 2014-07-25 09:36:28

Well, if something goes wrong during the boot process, systemd will fallback to verbose and show the log.. That happened to me when upgrading the linux kernel without upgrading virtualbox host modules.. But that was pretty clear to me because of a big red "FAILED" message instead of the usual "OK".

karol · 2014-07-25 10:21:39

Nah, the fsck doesn't show any problems, it just takes too long, see https://bbs.archlinux.org/viewtopic.php … 3#p1439403

If I remove 'quiet' (but keep systemd.show_status=0) I get a few extra lines about vmlinux and initramfs just after syslinux (my bootloader).
The only way not to see the shutdown stuff is close your eyes, I guess.

cafe · 2014-07-25 13:19:18

Oh, I seem to have missed that, somehow..
What's the size of your HD? Just out of curiosity..

karol · 2014-07-25 13:32:27

Blame ext3. It's only 40 GB divided in two partitions with /home being 30 GB.
Once I figure out some other things I'll do a reinstall (I don't want to convert it to ext4).

karol · 2014-07-25 18:21:25

https://bugs.freedesktop.org/show_bug.cgi?id=79582 says it's fixed, it's in the NEWS http://cgit.freedesktop.org/systemd/sys … v213#n1230 but I still see things that shouldn't be there ...

cafe · 2014-07-25 22:13:33

Most of the messages that appear during the shutdown process come from the kernel. To be honest, I don't know how to distinguish between kernel messages and systemd messages.. What are we trying to "shush", exactly?

karol · 2014-07-25 23:37:25

I see some lines about unmounting. https://bugs.archlinux.org/task/32673 is about systemd.

'systemd.show_status=0' works and even after fsck I don't see anything printed in the console (other than the prompt).

izmntuk · 2014-07-28 16:16:20

karol wrote:

https://bugs.freedesktop.org/show_bug.cgi?id=79582 says it's fixed, it's in the NEWS http://cgit.freedesktop.org/systemd/sys … v213#n1230 but I still see things that shouldn't be there ...

The annoying messages during shutdown progress are printed by /shutdown on initramfs(i.e. systemd-shutdown)

This bug is fixed during systemd v206-v208, and systemd v214.
In v215, the reason that the 'quiet' parameter on the kernel line have no effect on systemd-shutdown is: The 'quiet' parameter on kernel line should only apply to PID1. And the shutdown(i.e. systemd-shutdown) is not a PID1 process. AFAIK there is not any easy workaround except an upstream fix.

Last edited by izmntuk (2014-07-28 16:21:13)

Arch Linux

#1 2014-07-23 16:09:18

Hoiw to keep systemd quiet?

#2 2014-07-23 16:49:43

Re: Hoiw to keep systemd quiet?

#3 2014-07-24 12:33:07

Re: Hoiw to keep systemd quiet?

#4 2014-07-24 12:46:06

Re: Hoiw to keep systemd quiet?

#5 2014-07-24 13:31:10

Re: Hoiw to keep systemd quiet?

#6 2014-07-24 15:24:33

Re: Hoiw to keep systemd quiet?

#7 2014-07-24 15:41:21

Re: Hoiw to keep systemd quiet?

#8 2014-07-25 00:59:31

Re: Hoiw to keep systemd quiet?

#9 2014-07-25 01:14:19

Re: Hoiw to keep systemd quiet?

#10 2014-07-25 09:36:28

Re: Hoiw to keep systemd quiet?

#11 2014-07-25 10:21:39

Re: Hoiw to keep systemd quiet?

#12 2014-07-25 13:19:18

Re: Hoiw to keep systemd quiet?

#13 2014-07-25 13:32:27

Re: Hoiw to keep systemd quiet?

#14 2014-07-25 18:21:25

Re: Hoiw to keep systemd quiet?

#15 2014-07-25 22:13:33

Re: Hoiw to keep systemd quiet?

#16 2014-07-25 23:37:25

Re: Hoiw to keep systemd quiet?

#17 2014-07-28 16:16:20

Re: Hoiw to keep systemd quiet?

Board footer