I.Petrov wrote:

In case that you don't know the answer for this behavior yet. You see the messages due to the default settings of journald. The messages in every console should be stopped by setting

ForwardToWall=no

in /etc/systemd/journald.conf and can be directed to tty10 with

ForwardToConsole=yes TTYPath=/dev/tty10

The man page of journald.conf contains more information for each of the parameters.

Thank you, much appreciated. Shouldn't this really be the default setup for openSUSE ? -- Per Jessen, Zürich (1.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, In this case probably the messages are being forwarded to wall by your syslog daemon. Did you check the config files for the same? If you use rsyslog the following line *.emerg :omusrmsg:* in /etc/rsyslog.conf specifies that all emergency messages must be forwarded to wall for all logged in users. The level as well as the users however can be changed. Best Regards, I. Petrov On 03/08/2015 12:05 PM, Per Jessen wrote:

Per Jessen wrote:

...

I.Petrov wrote:

...

In case that you don't know the answer for this behavior yet. You see the messages due to the default settings of journald. The messages in every console should be stopped by setting

ForwardToWall=no

in /etc/systemd/journald.conf and can be directed to tty10 with

ForwardToConsole=yes TTYPath=/dev/tty10

The man page of journald.conf contains more information for each of the parameters.

Thank you, much appreciated.

It didn't really work though - I still get kernel messages such as:

[93647.616094] eth1: Auto-Negotiation unsuccessful, trying force link mode [93657.248166] eth1: Link down, cable problem? [93669.288119] eth1: Auto-Negotiation unsuccessful, trying force link mode [93678.920165] eth1: Link down, cable problem?

These are broadcast on all consoles.

My /etc/systemd/journald.conf contains:

[Journal] ForwardToWall=no ForwardToConsole=yes TTYPath=/dev/tty10

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJU/MmcAAoJEH8sJoKRFRU5JXoP/1zNIAQ1efchK04WSIluTgkv YSYHrp0R3VCKKmwqtd93mf1OJ50itxFMJZwghfWMvkMB+nVpZjiTuh5guBIEJZ2r P8oGFCZ3i2E/WRHtYtOyg0on3fwuHVK5V9f6kAEbEtJmUe1g6Em3+OgoYy+6+RSp d72zDRJAJBdTjElvdt5n3sZNN3elC6h+uBqUVQf77+ncHlaIlXeBLcdB2KmPWY9C 8ICE7brGajUSvaQTYBx+dKERl4H2R8uKzV4xfS8ppF7nBP87U+ho/eexFVfEFZVd lkL24mZemZYKphqEal6BhqBIRJ7IoWrELa+mDboau3Nr6GhEt69gTqTl2CTqVni6 rONHQJoWka7+kpU+nf3yV8Pu5mM2fEKbtKge9x436b3Tvcge+DjHMjRo6XWw1K/z ikXfR+MqS1Hu9A4GnJ+wgMhyblkLXOGySm7H24I7fvxo1sHh8uNBYr7Uo+G4lMpQ g0aoQ+ITvqRA7MeYEcS23nw1leEcFoYvzfdWbtU2dgAsNGzopnPHtfMn5OCJ3yx+ 3Rcq4+mvQnIJQlZP/GnEXFKX+R+0o5BKZ/Q/9nnYGU6bD51tBhioVqud1LbuWMru SI7tg4NwJRhGZL5LsjycJBspa35EQkmmtUeLY9cTCr5zj43nqj2HjuD766ZwprBy yLUo/1dcaERRuA1g1Hl7 =5JWq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen wrote:

I.Petrov wrote:

...

In this case probably the messages are being forwarded to wall by your syslog daemon. Did you check the config files for the same? If you use rsyslog the following line

I have syslog-ng with this config (the default) for console messages:

# # Most warning and errors on tty10 and on the xconsole pipe: # destination console { file("/dev/tty10" suppress(30) owner(-1) group(-1) perm(-1)); }; log { source(src); source(chroots); filter(f_console); destination(console); };

destination xconsole { pipe("/dev/xconsole" suppress(30) owner(-1) group(-1) perm(-1)); }; log { source(src); source(chroots); filter(f_console); destination(xconsole); };

Are you sure it's a 'wall' ? To me it seems more like the kernel messages are printed on the currently active console. I'll have to double check, but I don't recall seeing the same messages on every console.

Have checked, the kernel messages only go to the currently active console, not to every one. I have determined that I can control the messages by changing /proc/sys/kernel/printk, but I still don't know how to direct them to just one console (and always the same one). -- Per Jessen, Zürich (5.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov wrote:

В Mon, 09 Mar 2015 08:47:20 +0100 Per Jessen пишет:

...

Have checked, the kernel messages only go to the currently active console, not to every one. I have determined that I can control the messages by changing /proc/sys/kernel/printk, but I still don't know how to direct them to just one console (and always the same one).

Try passing console=tty1 on kernel command line.

Just tried it, didn't work - the messages still appear on the currently active/visible console. Did something change in this respect? I don't have reason to work on the physical console very much, but I don't remember this behaviour from older systems (this one is 13.1). -- Per Jessen, Zürich (8.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov wrote:

В Mon, 09 Mar 2015 10:52:52 +0100 Per Jessen пишет:

...

Andrei Borzenkov wrote:

...

В Mon, 09 Mar 2015 08:47:20 +0100 Per Jessen пишет:

...

Have checked, the kernel messages only go to the currently active console, not to every one. I have determined that I can control the messages by changing /proc/sys/kernel/printk, but I still don't know how to direct them to just one console (and always the same one).

Try passing console=tty1 on kernel command line.

Just tried it, didn't work - the messages still appear on the currently active/visible console. Did something change in this respect? I don't have reason to work on the physical console very much, but I don't remember this behaviour from older systems (this one is 13.1).

For all I remember kernel always printed messages on currently opened foreground tty by default. To change it use

/usr/sbin/klogconsole -r n

where n is tty number. May be it could be integrated in systemd (this is single ioctl after all).

I've found the issue - it's a matter of the printk levels. On an openSUSE 11.0 system, the default was "1 4 1 7", on a 13.1 system it's "7 4 1 7". That's why I'm seeing so much output. If that's intentional, it would sure make sense to direct it all to tty10. For myself, I'll adjust the printk levels. /Per -- Per Jessen, Zürich (12.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov wrote:

В Mon, 09 Mar 2015 17:43:47 +0100 Per Jessen пишет:

...

I've found the issue - it's a matter of the printk levels. On an openSUSE 11.0 system, the default was "1 4 1 7", on a 13.1 system it's "7 4 1 7". That's why I'm seeing so much output.

If that's intentional, it would sure make sense to direct it all to tty10. For myself, I'll adjust the printk levels.

"7" is default console level for printk. Before systemd it was usually adjusted in one of startup scripts (dmesg -n).

Aha, so this could be a regression. On my 11.0 systems, I see the following in /etc/init.d/boot.klog: if test -x /usr/sbin/klogconsole ; then if test -x /sbin/showconsole ; then if test "`/sbin/showconsole`" = /dev/tty1 ; then ( test -c /dev/tty10 && > /dev/tty10 ) > /dev/null 2>&1 \ && /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r10 else /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r 0 fi fi elif test -x /bin/dmesg ; then /bin/dmesg -n 7 fi I don't know how kernel.printk gets adjusted to "1 4 1 7". -- Per Jessen, Zürich (9.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov wrote:

В Mon, 09 Mar 2015 18:57:48 +0100 Per Jessen пишет:

...

Andrei Borzenkov wrote:

...

В Mon, 09 Mar 2015 17:43:47 +0100 Per Jessen пишет:

...

I've found the issue - it's a matter of the printk levels. On an openSUSE 11.0 system, the default was "1 4 1 7", on a 13.1 system it's "7 4 1 7". That's why I'm seeing so much output.

If that's intentional, it would sure make sense to direct it all to tty10. For myself, I'll adjust the printk levels.

"7" is default console level for printk. Before systemd it was usually adjusted in one of startup scripts (dmesg -n).

Aha, so this could be a regression. On my 11.0 systems, I see the following in /etc/init.d/boot.klog:

if test -x /usr/sbin/klogconsole ; then if test -x /sbin/showconsole ; then if test "`/sbin/showconsole`" = /dev/tty1 ; then ( test -c /dev/tty10 && > /dev/tty10 ) > /dev/null 2>&1 \ && /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r10 else /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r 0 fi fi elif test -x /bin/dmesg ; then /bin/dmesg -n 7 fi

I don't know how kernel.printk gets adjusted to "1 4 1 7".

One one of 13.2 printk level is "1" and on another it is "4". It is set to "1" by klogd.service. But I was not able to find out where it is set to "4".

On the system I am testing with currently, klogd is disabled: # systemctl status klogd.service klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled) Active: inactive (dead)

Also apparently openSUSE journald includes patch to redirect printk messages to /dev/tty10. This does not happen on at least one system either. One difference is, system where messages go to active tty has two console drivers. I suspect loading second driver resets setting made by journald earlier.

This is real mess.

I think I'll open a bugreport. -- Per Jessen, Zürich (8.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Mar 11, 2015 at 11:57 AM, Per Jessen wrote:

Per Jessen wrote:

...

On the system I am testing with currently, klogd is disabled:

# systemctl status klogd.service klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled) Active: inactive (dead)

See bug#921510 for a reason why klogd is installed, but left disabled.

This is general rule - services must be explicitly whitelisted to be enabled automatically after installation. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Mar 11, 2015 at 12:28 PM, Per Jessen wrote:

Andrei Borzenkov wrote:

...

On Wed, Mar 11, 2015 at 11:57 AM, Per Jessen wrote:

...

Per Jessen wrote:

...

On the system I am testing with currently, klogd is disabled:

# systemctl status klogd.service klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled) Active: inactive (dead)

See bug#921510 for a reason why klogd is installed, but left disabled.

This is general rule - services must be explicitly whitelisted to be enabled automatically after installation.

What does "whitelisted" mean in this context?

systemd-presets-branding-openSUSE package contains list of services (/usr/lib/systemd/system-preset/90-default-openSUSE.preset) that are enabled by default when installed. You can of course override it (provide your own default that will enable everything). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Mar 11, 2015 at 1:33 PM, Per Jessen wrote:

Andrei Borzenkov wrote:

...

On Wed, Mar 11, 2015 at 12:28 PM, Per Jessen wrote:

...

Andrei Borzenkov wrote:

...

On Wed, Mar 11, 2015 at 11:57 AM, Per Jessen wrote:

...

Per Jessen wrote:

...

On the system I am testing with currently, klogd is disabled:

# systemctl status klogd.service klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled) Active: inactive (dead)

See bug#921510 for a reason why klogd is installed, but left disabled.

This is general rule - services must be explicitly whitelisted to be enabled automatically after installation.

What does "whitelisted" mean in this context?

systemd-presets-branding-openSUSE package contains list of services (/usr/lib/systemd/system-preset/90-default-openSUSE.preset) that are enabled by default when installed. You can of course override it (provide your own default that will enable everything).

Ah, okay, thanks. I'll enable klog{d} explicitly, it just seems to me it ought to be the default in order to retain the previous behavior.

If you mean it was enabled in the past during new installation by default, then it can be considered regression. If you mean you updated your system and it was enabled before update and became disabled after update - this sounds like a bug for me.

Never mind, the maintainer disagrees and I can't be bothered.

Maintainer disagrees to enabling it by default. It is not clear if you both mean the same thing here :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org