[Mageia-dev] [RFC] rsyslog vs journalctl

Pascal Terjan pterjan at gmail.com
Fri Feb 8 11:33:56 CET 2013


On Fri, Feb 8, 2013 at 10:31 AM, Pascal Terjan <pterjan at gmail.com> wrote:
> On Fri, Feb 8, 2013 at 9:54 AM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
>> 'Twas brillig, and AL13N at 07/02/13 18:40 did gyre and gimble:
>>> Op donderdag 7 februari 2013 13:34:06 schreef Colin Guthrie:
>>>> 'Twas brillig, and AL13N at 07/02/13 11:40 did gyre and gimble:
>>> [...]
>>>>> what about the tty12 bug? can this be fixed with journald? it seems to be
>>>>> a feature that people don't want to lose?
>>>>
>>>> Not sure. I'll find out. It should be trivial really... i.e. all it
>>>> really needs is a journalctl -f command run on tty12. You could craft an
>>>> agetty command that worked like that easily enough, although there may
>>>> be something more elegant that is more efficient and cleaner.
>>>
>>> since the tty12 "feature" is present now, it would be nice if it could still
>>> be there and started as soon as possible, just like before.
>>
>> Just to try it, can you set:
>>
>> TTYPath=/dev/tty12
>> ForwardToConsole=yes
>>
>> in /etc/systemd/journald.conf
>>
>>
>> I'm not 100% sure whether it really should be available by default tho'.
>> I mean, if you are a logged in user you cannot view the system logs
>> unless you are in the adm group or root. Why should you just be able to
>> see it via switching to a tty? Seems somewhat counter intuitive to me.
>
> I think it used to be enabled or not by msec depending on security level

/usr/share/msec/plugins/msec.py:    def enable_console_log(self, arg,
expr='*.*', dev='tty12'):


More information about the Mageia-dev mailing list