On Wed, Nov 21, 2012 at 11:35 PM, Karol Blazewicz

wrote:

On Wed, Nov 21, 2012 at 5:00 PM, Sudaraka Wijesinghe 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: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 11/22/12 05:10, Ray Kohler wrote:

On Wed, Nov 21, 2012 at 5:55 PM, Sudaraka Wijesinghe 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?

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 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

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.

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 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