[systemd-devel] Keeping console messages on VT1

Mirco Tischler mt-ml at gmx.de
Wed Sep 26 16:22:54 PDT 2012

2012/9/27 Henrik /KaarPoSoft <henrik at kaarposoft.dk>:
> On 09/27/12 00:05, Tom Gundersen wrote:
>> On Thu, Sep 27, 2012 at 12:02 AM, Henrik /KaarPoSoft
>> <henrik at kaarposoft.dk> wrote:
>>> (b) Is there a way to have logind NOT show a login prompt on VT1?
>> It is not logind that starts login, but getty. You want to disable
>> getty at tty1.service, and enable say getty at tty2.service instead.
>> -t
> DOH!
> If I move
> /etc/systemd/system/getty.target.wants/getty at tty1.service
> to
> /etc/systemd/system/getty.target.wants/getty at tty2.service
> this annoyance is gone.
> Thank you, Tom!
> (but of course I still get console messages on the current VT, not VT1)
> /Henrik
> _______________________________________________
I haven't tried this and maybe it won't work, but you can set TTYPath
to /dev/tty1 in journald.conf. But I suppose you will still get kernel
messages, as they don't go through the journal (quiet on the kernel
commandline gets rid of the unimportant ones).


More information about the systemd-devel mailing list