systemd boot messages in the login prompt

Hi,I just switched to systemd and there is one thing left bothering me - after the login prompt appears, systemd keeps spamming messages about some services starting (mysql, ntp...). I've googled a little and found that this should have been fixed some time ago by adding the Type=idle parameter, which is already set in my getty service file (/usr/lib/systemd/system/getty@.service) without any results.Thanks

Re: systemd boot messages in the login prompt

I have the same situation !!!

I dont know maybe is not proper to write about it in "Applications & Desktop Environments" but rather in "Arch Discussion" (systemd is part of Arch now) or in "Pacman & Package Upgrade Issues" (this issue appers right after upgrade).

Nevertheless, I have the same situation.

I updated the system. During update some packages were replaced with 'systemd'. Then suggestion appeared - to append 'init=/bin/systemd' to kernel command line options in your bootloader. I have syslinux as bootloader.I did it. After reboot a lot of messages appeared.[ OK ] ..........[ OK ] ..........[ OK ] ..........

Re: systemd boot messages in the login prompt

Well, i don't think it is really a bug. It is a matter of service booting order. For me, i just move the getty service to graphical target so that it will spwan at the end of the booting. Then, there is no more overlapped message.

Re: systemd boot messages in the login prompt

The following has happened to me on multiple (fresh) installations:

After following the directions here: https://wiki.archlinux.org/index.php/Ne … _Operation to set up a static wired connection, I'm seeing curious behavior when the system boots. Specifically, the login prompt appears before the boot process is complete. So I end up with a screen looking like this:

There's a blinking cursor on the next line after that. It's not really a big deal, since I can just press enter and get a fresh login prompt. However, it violates my sense of having things clean and orderly. I did a fair amount of searching, but didn't find any reference to this occurance. Though, like I said, I've seen it multiple times. Has anyone else seen this and is there a fix?

Re: systemd boot messages in the login prompt

I don't mean to necro an old thread, but it doesn't look like this was resolved for OP and it's a problem that irritated me for a long time as well (because just setting systemd to quiet mode was a poor solution).

After some research I found a good solution on the Mageia bug tracker that I've been using for a few months..

Just add the following line to the top of the [Service] section in /usr/lib/systemd/system/getty@.service :

Re: systemd boot messages in the login prompt

Better yet, do this:[snip]That way you get the updates. I chose to use the .include function rather than the foo.service.d type because I am not sure how well the latter works on "@" services.

Now I am going to be really late for work!

I'm not sure if I understand the implementation properly.. Do you have all of that in a /etc/systemd/system/getty@.service file?

Yes, you include the original file and add some extra options to it. With recent systemd versions you can add multiple of these 'extensions' in the form of .conf files in a directory named after the service as in the wiki page I linked to (so .include line is no longer needed). Works fine for getty@.service, but I haven't tried it with template instances yet (as in getty@tty1.service).

Re: systemd boot messages in the login prompt

Re: systemd boot messages in the login prompt

It doesn't look like the upstream bug report (see above) is getting any developer attention and posting here is not going to change that. I use quiet anyway, so I don't care, but how much trouble is it to drop a 2-line .conf file under /etc if it really bothers you?

Re: systemd boot messages in the login prompt

Excuse my ignorance, but I thought it was a .service file and that you were only adding "ExecStartPre=-/bin/kill -55 1" under [Service]. I most likely misunderstood something because I still have the issue.

Re: systemd boot messages in the login prompt

You can also use a 3-line .service file (with .include) or (preferably not) copy the original in its entirety and add that line (this has all been explained in this thread). But if you go with a .service file, you also have to reenable getty@tty1 so the symlink in multi-user.target.wants points to your new file under /etc instead of the original under /usr.

Re: systemd boot messages in the login prompt

I have this aswell, but i think i remember it happen before systemd at some point aswell.The thing is also, that since some time ago one could write over/delete the characters of the actual prompt (i think that is still the case)

But yeah, this issue is annoying, it only happens sometimes (due to however fast the "services" start) but it is very confusing.I am a bit worried that many people expect/use a login to X/graphic manager, thus this bug gets too little attention.

Re: systemd boot messages in the login prompt

PReP wrote:

I have this aswell, but i think i remember it happen before systemd at some point aswell.The thing is also, that since some time ago one could write over/delete the characters of the actual prompt (i think that is still the case)

But yeah, this issue is annoying, it only happens sometimes (due to however fast the "services" start) but it is very confusing.I am a bit worried that many people expect/use a login to X/graphic manager, thus this bug gets too little attention.

I too have a vague recollection of this occuring before systemd as well. But I am not 100% about that...

Honestly, with your concerns about people's exectations, if a non-*nix user is looking at a Linux machine, I don't think they really know what to expect. In fact, a text based login prompt is likely just as confusing to them as a login prompt that is polluted with boot messages as well.

These issues went away for me when I started using a SSD, so it is indeed an issue with parallel starting of services. The thing is, we all enjoy the benefits of systemd's parallel startup, it provides a much faster boot. So most of us remove the scrolling messages because it is typically scrolling too fast to make sense of anyway. But for those of you who still want those messages, you can't have the expectation that it is going to tell you about all your messages and not mess up your login prompt, knowing that parallel forces are afoot. If it were to simply throw out the last boot messages in favor or having a clean login prompt, I think then you would likely have people thinking that some of their services weren't starting or, worse, people who knew what was happening but now complained of inconsistent boot message output.

What I am trying to say is that systemd is actually doing exactly what you are asking of it. If you don't use the 'quiet' boot parameter, it is going to tell you about the crap that is is doing. If you don't intentionally use ordering or some other functionality to make sure that getty@tty1 is started after everything else, it is going to do what the system is asking of it.