[opensuse] Unwanted kernel messages on VTs
Up until 13.2, skipping 13.1, I could login to one of the VTs (via cntrl-alt-F#) and there were never any kernel messages displayed on that VT while you were there. Even when using kernel command line options of "splash=verbose" as opposed to "splash=silent quiet". I can't seem to get rid of these. "splash=silent quiet" is not an option for me as I must have verbose kernel messages here. I thought maybe it was a systemd thing (and I still do) so I uninstalled systemd-logger and installed good old syslog-ng. But that didn't help. Neither kernel or syslog output should be going to my VT. Why does it? Is it systemd? How can I get a "clean" VT without "splash=silent quiet" like I could on SuSE releases prior to 13.2? Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-02 16:46, Mark Hounschell wrote:
Neither kernel or syslog output should be going to my VT. Why does it? Is it systemd? How can I get a "clean" VT without "splash=silent quiet" like I could on SuSE releases prior to 13.2?
Try "klogconsole -r 10" and they should go to tty10. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 12/02/2014 10:52 AM, Carlos E. R. wrote:
On 2014-12-02 16:46, Mark Hounschell wrote:
Neither kernel or syslog output should be going to my VT. Why does it? Is it systemd? How can I get a "clean" VT without "splash=silent quiet" like I could on SuSE releases prior to 13.2?
Try "klogconsole -r 10" and they should go to tty10.
That does what I needed. Thanks. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-02 17:00, Mark Hounschell wrote:
On 12/02/2014 10:52 AM, Carlos E. R. wrote:
On 2014-12-02 16:46, Mark Hounschell wrote:
Neither kernel or syslog output should be going to my VT. Why does it? Is it systemd? How can I get a "clean" VT without "splash=silent quiet" like I could on SuSE releases prior to 13.2?
Try "klogconsole -r 10" and they should go to tty10.
That does what I needed. Thanks.
Good :-) I found that trick several years ago, because when running vmware the kernel messages started appearing on tty1 or elsewhere, and this command sent them again to tty10. It is not absolutely permanent, though. Curious that you have that problem now. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 12/03/2014 09:39 PM, Carlos E. R. wrote:
On 2014-12-02 17:00, Mark Hounschell wrote:
On 12/02/2014 10:52 AM, Carlos E. R. wrote:
On 2014-12-02 16:46, Mark Hounschell wrote:
Neither kernel or syslog output should be going to my VT. Why does it? Is it systemd? How can I get a "clean" VT without "splash=silent quiet" like I could on SuSE releases prior to 13.2?
Try "klogconsole -r 10" and they should go to tty10.
That does what I needed. Thanks.
Good :-)
I found that trick several years ago, because when running vmware the kernel messages started appearing on tty1 or elsewhere, and this command sent them again to tty10. It is not absolutely permanent, though.
Curious that you have that problem now.
Yes, it is "Curious". I'll just blame it on systemd and move on though. Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Dec 04, 2014 at 10:58:17AM -0500, Mark Hounschell wrote:
On 12/03/2014 09:39 PM, Carlos E. R. wrote:
On 2014-12-02 17:00, Mark Hounschell wrote:
On 12/02/2014 10:52 AM, Carlos E. R. wrote:
On 2014-12-02 16:46, Mark Hounschell wrote:
Neither kernel or syslog output should be going to my VT. Why does it? Is it systemd? How can I get a "clean" VT without "splash=silent quiet" like I could on SuSE releases prior to 13.2?
Try "klogconsole -r 10" and they should go to tty10.
That does what I needed. Thanks.
Good :-)
I found that trick several years ago, because when running vmware the kernel messages started appearing on tty1 or elsewhere, and this command sent them again to tty10. It is not absolutely permanent, though.
Curious that you have that problem now.
Yes, it is "Curious". I'll just blame it on systemd and move on though.
linux:~ # grep klogconsole /usr/lib/systemd/system/* -s /usr/lib/systemd/system/klog.service:ExecStart=/bin/sh -c "test -c /dev/tty10 && /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r10 || :" linux:~ # rpm -qf /usr/lib/systemd/system/klog.service syslog-service-2.0-774.23.noarch this has nothing todo with systemd (nor with SysVinit) Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On 2014-12-05 11:23, Dr. Werner Fink wrote:
On Thu, Dec 04, 2014 at 10:58:17AM -0500, Mark Hounschell wrote:
On 12/03/2014 09:39 PM, Carlos E. R. wrote:
Curious that you have that problem now.
Yes, it is "Curious". I'll just blame it on systemd and move on though.
linux:~ # grep klogconsole /usr/lib/systemd/system/* -s /usr/lib/systemd/system/klog.service:ExecStart=/bin/sh -c "test -c /dev/tty10 && /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r10 || :" linux:~ # rpm -qf /usr/lib/systemd/system/klog.service syslog-service-2.0-774.23.noarch
this has nothing todo with systemd (nor with SysVinit)
Well, on 13.2 syslog-service is not installed by default, but journalctl, which is indeed a systemd thing :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (3)
-
Carlos E. R. -
Dr. Werner Fink -
Mark Hounschell