[arch-general] Polluted login prompt
Hey Archers, This is an issue I has since the day I switched to systemd, I was hoping it would get fixed eventually but seems not. I start both Apache and MySQL services on boot, and both of them display the start complete message after the login prompt. Something like this:
Starting MySQL Starting Apache login: [ OK ] MySQL started [ OK ] Apache started
Although this doesn't break anything it just doesn't look nice. (BTW, I'm not using any DM and getty is set NOT to clear any boot messages) I saw this already reported as a bug https://bugs.freedesktop.org/show_bug.cgi?id=54247, but seems there is no fix yet. Can anyone tell me how I might be able to get a clean login prompt? Thanks. -- Sudaraka Wijesinghe.
On Wed, Nov 21, 2012 at 5:00 PM, Sudaraka Wijesinghe <sudaraka.wijesinghe@gmail.com> wrote:
Can anyone tell me how I might be able to get a clean login prompt?
Have you tried adding 'quiet' to the kernel boot line?
On Wed, Nov 21, 2012 at 11:35 PM, Karol Blazewicz <karol.blazewicz@gmail.com
wrote:
On Wed, Nov 21, 2012 at 5:00 PM, Sudaraka Wijesinghe <sudaraka.wijesinghe@gmail.com> wrote:
Can anyone tell me how I might be able to get a clean login prompt?
Have you tried adding 'quiet' to the kernel boot line?
Same thing here, though a fast disk prevents it for me. At work, I have a regular 7200RPM HDD and the last 3-4 lines of the boot process get displayed after the login prompt. On my laptop with and SSD, everything gets started before the login prompt, so no pollution.
On 11/22/12 03:11, D. Can Celasun wrote:
Same thing here, though a fast disk prevents it for me.
I wonder if there is some sort of mechanism to make those services load quietly without them reporting back the [ok] message.
On 11/22/12 03:05, Karol Blazewicz wrote:
Have you tried adding 'quiet' to the kernel boot line?
This doesn't help because the messages in question are generated by the systemd unit loading process, not the Kernel. Thanks.
On Wed, Nov 21, 2012 at 5:55 PM, Sudaraka Wijesinghe <sudaraka.wijesinghe@gmail.com> wrote:
On 11/22/12 03:05, Karol Blazewicz wrote:
Have you tried adding 'quiet' to the kernel boot line?
This doesn't help because the messages in question are generated by the systemd unit loading process, not the Kernel.
Have you tested it? systemd reads the kernel log level as well, so the "quiet" parameter does indeed make all the systsemd status messages not appear at all.
On 11/22/12 05:10, Ray Kohler wrote:
On Wed, Nov 21, 2012 at 5:55 PM, Sudaraka Wijesinghe <sudaraka.wijesinghe@gmail.com> wrote:
On 11/22/12 03:05, Karol Blazewicz wrote:
Have you tried adding 'quiet' to the kernel boot line?
This doesn't help because the messages in question are generated by the systemd unit loading process, not the Kernel.
Have you tested it? systemd reads the kernel log level as well, so the "quiet" parameter does indeed make all the systsemd status messages not appear at all.
Yes, my earlier comment was after testing it. And since several of you have mentioned that it works, I just tried it again and it does NOT make the systemd quite. Any idea why it is behaving differently for me?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/21/2012 07:25 PM, Sudaraka Wijesinghe wrote:
On 11/22/12 05:10, Ray Kohler wrote:
On Wed, Nov 21, 2012 at 5:55 PM, Sudaraka Wijesinghe <sudaraka.wijesinghe@gmail.com> wrote:
On 11/22/12 03:05, Karol Blazewicz wrote:
Have you tried adding 'quiet' to the kernel boot line?
This doesn't help because the messages in question are generated by the systemd unit loading process, not the Kernel.
Have you tested it? systemd reads the kernel log level as well, so the "quiet" parameter does indeed make all the systsemd status messages not appear at all.
Yes, my earlier comment was after testing it. And since several of you have mentioned that it works, I just tried it again and it does NOT make the systemd quite.
Any idea why it is behaving differently for me?
quiet quite -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQrXd8AAoJEKPIShkjPu5/yvsH/RXebTsQN96gM/FaYsIyWHkI oSlAMJGEEFwalvo9B0y3gpxz3/RgbeVlnWPn4FU0DvDFhx2/jdphe7TEGyTL2QNe aA5lOQKj8BX0N2IiyTPbcosmeaRJtua9bdyd07UFQERcL8itse/x5n53+CanHBNI sAzLSe2zJ03F/U4uNAq5L4fas4UpKeyIZa57H93S4GGARfHL1EvuJGAhrhcptsYu dABBSVWdLCAJAmXGft831Wk7NoJfE0RLm1TfGkDw7HSbaGwVgCXiFeVDPDCFNdXA Io579IN0aMCuRGMFzlDF1iiNiJ/QFuXRBjF11g6qK+JgBBQ412Z9lJTRE1zCPjY= =1FJw -----END PGP SIGNATURE-----
On 11/22/12 06:23, Ashim Acharya wrote:
quiet quite
Aha, yes I did misspell that on command line also. good catch. And, yes it does quiet down everything. Problem is that it's too quiet now and even suppressing the possible error messages. So I don't think this (kernel boot parameter quiet) is the right answer to my problem. Thanks.
On Wed, Nov 21, 2012 at 10:16 PM, Sudaraka Wijesinghe < sudaraka.wijesinghe@gmail.com> wrote:
Problem is that it's too quiet now and even suppressing the possible error messages.
This is something I'm looking for too, I would like to see no messages except for the FAIL ones. Time to drop-by at the systemd's lair and make a wish?
On Thursday 22 Nov 2012 01:07:22 Martín Cigorraga wrote:
On Wed, Nov 21, 2012 at 10:16 PM, Sudaraka Wijesinghe <
sudaraka.wijesinghe@gmail.com> wrote:
Problem is that it's too quiet now and even suppressing the possible error messages.
This is something I'm looking for too, I would like to see no messages except for the FAIL ones. Time to drop-by at the systemd's lair and make a wish?
I don't think "quiet" silences error messages. For instance, I still see fsck messages and a warning related to my unsupported SD-card reader when I boot. I'm pretty sure there's a log level threshold under which quiet suppresses the messages, and I think you can change that threshold with another parameter if you want. Sorry to be so vague; I can't check those details right now. Paul
On Thu, 22 Nov 2012 01:07:22 -0300 Martín Cigorraga <msx@archlinux.us> wrote:
On Wed, Nov 21, 2012 at 10:16 PM, Sudaraka Wijesinghe < sudaraka.wijesinghe@gmail.com> wrote:
Problem is that it's too quiet now and even suppressing the possible error messages.
This is something I'm looking for too, I would like to see no messages except for the FAIL ones. Time to drop-by at the systemd's lair and make a wish?
No. From man systemd: * systemd.show_status= Takes a boolean argument. If true shows terse service status updates on the console during bootup. Defaults to true, unless quiet is passed as kernel command line option in which case it defaults to false. * quiet If passed turns off status output at boot, much like systemd.show_status=false would. Note that this option is also read by the kernel itself and disables kernel log output to the kernel. Passing this option hence turns off the usual output from both the system manager and the kernel. HTH, -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Am 22.11.2012 02:16, schrieb Sudaraka Wijesinghe:
On 11/22/12 06:23, Ashim Acharya wrote:
quiet quite
Aha, yes I did misspell that on command line also. good catch. And, yes it does quiet down everything.
Problem is that it's too quiet now and even suppressing the possible error messages.
The nice thing about systemd is that you can still look up all errors using 'systemctl --failed', the journal and 'systemctl status ...'. The output on the console does not have much value anyway.
Problem is that it's too quiet now and even suppressing the possible error messages. So I don't think this (kernel boot parameter quiet) is the right answer to my problem.
Is there no way to redirect the output to a seperate terminal. It took some rather longer commands than I'd like and symlink fiddling to do that on the systemd setup I tried a while back but I'm not sure if it included systemd output? I could check but don't know as I rarely use that system? -- _______________________________________________________________________ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) _______________________________________________________________________
On 22/11/12, Sudaraka Wijesinghe wrote: | This doesn't help because the messages in question are generated by the | systemd unit loading process, not the Kernel. Adding quiet to the kernel command line will make systemd quiet. Give it a go. -- Simon Perry (aka Pezz)
On 21/11/12 16:00, Sudaraka Wijesinghe wrote:
I start both Apache and MySQL services on boot, and both of them display the start complete message after the login prompt.
Something like this:
Starting MySQL Starting Apache login: [ OK ] MySQL started [ OK ] Apache started
Although this doesn't break anything it just doesn't look nice. (BTW, I'm not using any DM and getty is set NOT to clear any boot messages)
I had this exact same problem with certain services spewing messages over my login prompt. I solved it by adding a slight delay to the startup of the offending service. That is, I created a file like this: [Timer] OnActiveSec=30 And saved it as /etc/systemd/system/multi-user.target.wants/httpd.timer. See man systemd.timer for further info. HTH
On 11/22/12 at 06:19pm, kachelaqa wrote:
On 21/11/12 16:00, Sudaraka Wijesinghe wrote:
I start both Apache and MySQL services on boot, and both of them display the start complete message after the login prompt.
Something like this:
Starting MySQL Starting Apache login: [ OK ] MySQL started [ OK ] Apache started
Although this doesn't break anything it just doesn't look nice. (BTW, I'm not using any DM and getty is set NOT to clear any boot messages)
I had this exact same problem with certain services spewing messages over my login prompt.
I solved it by adding a slight delay to the startup of the offending service.
That is, I created a file like this:
[Timer] OnActiveSec=30
And saved it as /etc/systemd/system/multi-user.target.wants/httpd.timer.
See man systemd.timer for further info.
HTH
I noticed that when I turned down logging to the console in journald.conf it started only telling me the fsck status of / instead of all of the partitions. So maybe there is some happy medium that you may be able to find without the quiet parameter and a lower "MaxLevelConsole=" setting. I cannot remember what level it was though, I want to say it was the equivalent to 3, but I am not certain. I have since gone back to defaults and have to agree with the sentiments of others that the quiet parameter with "systemctl --failed" is perfect. The speed at which the boot stuff whizzes by is too fast to really be usable anyway (though I am an SSD user). -- Curtis Shimamoto sugar.and.scruffy@gmail.com
participants (13)
-
Ashim Acharya
-
Curtis Shimamoto
-
D. Can Celasun
-
kachelaqa
-
Karol Blazewicz
-
Kevin Chadwick
-
Leonid Isaev
-
Martín Cigorraga
-
Paul Gideon Dann
-
Ray Kohler
-
Simon Perry
-
Sudaraka Wijesinghe
-
Thomas Bächler