Hmm, it might be my system configuration or a kernel bug, not systemd. The thing is that kernel messages instead of being outputted to /dev/console are outputted to the currently active VT.
I use metalog as the syslog and when it's run, these messages aren't outputted to the VT. I saw that journald reads kernel messages and stores them in its logs, so I was wondering whether it's supposed to intercept/block that output like syslogs or not. On 5 July 2013 22:23, Lennart Poettering <[email protected]> wrote: > On Thu, 04.07.13 14:38, Tomasz Sobczyk ([email protected]) wrote: > >> Hi, >> >> Is the fact that journald reads the kernel log, but doesn't prevent >> the messages from outputting to the active terminal a bug or desired >> behaviour? >> >> # echo "Test" > /dev/kmsg >> Test >> # >> >> If I, let's say, connect a USB device then the active terminal is >> spammed with the kernel log messages. I can prevent this by starting a >> system logger, but with journald running I shouldn't need another one, >> right? > > The log messages the kernel forwards to the console may be configured > using /proc/sys/kernel/printk, and that's hardly something for journald > to configure. See "man 5 proc" for details on tha file. > > Lennart > > -- > Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
