Does anyone know how to disable console messages?
I have a small embedded Linux system running a graphical app which uses QT to access the frame buffer directly. However, when the app is running, I get console messages printed on the screen, thus corrupting it. The sort of message I get are eg notification of eth0 up or down, etc.
Many thanks,
Stuart.
On Tuesday 10 May 2005 7:59 pm, Stuart Bailey wrote:
Does anyone know how to disable console messages?
I think this is controlled by /etc/syslog.conf
Looking at mine
kern.warning;*.err;authpriv.none /dev/tty10 kern.warning;*.err;authpriv.none |/dev/xconsole *.emerg *
I would try commenting out that bottom line, I think you can ignore the next one up as that is a named pipe for what I think was the little log that used to appear at the bottom of the desktop of some distros.
On 10-May-05 Stuart Bailey wrote:
Does anyone know how to disable console messages?
I have a small embedded Linux system running a graphical app which uses QT to access the frame buffer directly. However, when the app is running, I get console messages printed on the screen, thus corrupting it. The sort of message I get are eg notification of eth0 up or down, etc.
Many thanks,
Stuart.
On the assumption that the application is writing its messages to "stderr", try modifying the command that starts the app from
app_cmd ...
to
app_cmd ... 2>/dev/null
This redirects the stderr stream to /dev/null which will silently swallow it.
On the other hand it might just be writing these status messages to the "stdout" stream, in which case you can sink these with
app_cmd ... 1>/dev/null
(or even use both together). However, I'm a bit dubious about the wisdom of sinking stdout!
Hoping this helps, Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 10-May-05 Time: 20:15:15 ------------------------------ XFMail ------------------------------
Hi Ted, Sorry, perhaps I wasn't to clear. It's not the app that's generating the messages, it's the system. For instance, if I unplug my ethernet cable, I get:
eth0: Autonegotiation advertising 0x5e1 partner 0x00 eth0: link down.
displayed on screen, corrupting my GUI.
Googling seems to suggest that ssyslogd needs a config file (/etc/syslog.conf). Unfortunately, the syslogd I'm using comes as part of busybox, and it ignores /etc/syslog.conf.
Many thanks,
Stuart.
On Tuesday 10 May 2005 20:15, Ted Harding wrote:
On 10-May-05 Stuart Bailey wrote:
Does anyone know how to disable console messages?
I have a small embedded Linux system running a graphical app which uses QT to access the frame buffer directly. However, when the app is running, I get console messages printed on the screen, thus corrupting it. The sort of message I get are eg notification of eth0 up or down, etc.
Many thanks,
Stuart.
On the assumption that the application is writing its messages to "stderr", try modifying the command that starts the app from
app_cmd ...
to
app_cmd ... 2>/dev/null
This redirects the stderr stream to /dev/null which will silently swallow it.
On the other hand it might just be writing these status messages to the "stdout" stream, in which case you can sink these with
app_cmd ... 1>/dev/null
(or even use both together). However, I'm a bit dubious about the wisdom of sinking stdout!
Hoping this helps, Ted.
E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 10-May-05 Time: 20:15:15 ------------------------------ XFMail ------------------------------
On Tuesday 10 May 2005 9:03 pm, Stuart Bailey wrote:
Googling seems to suggest that ssyslogd needs a config file (/etc/syslog.conf). Unfortunately, the syslogd I'm using comes as part of busybox, and it ignores /etc/syslog.conf.
Ahh that would be a bit of a problem. Looks horribly like a rebuild of busybox may be in order to me.
Or perhaps try calling syslogd with the -K option (assuming all the messages are bothering you are comming from the kernel) but then of course that is a bit of a bodge because now you have no kernel logging. The -K option seems to be unique to the busybox version of syslogd BTW
-------------------------------------------------------
If your copy is compiled with support for circular logging, try running syslogd with '-C 16'.
I rebuilt BusyBox with circular logging support (only 8K though) and ran syslogd with -m 0 -C 8
This had no effect.
I've also tried running klogd along side, but the messages are displayed on screen and in the log.
Stuart.
On Tuesday 10 May 2005 9:03 pm, Stuart Bailey wrote:
Googling seems to suggest that ssyslogd needs a config file (/etc/syslog.conf). Unfortunately, the syslogd I'm using comes as part of busybox, and it ignores /etc/syslog.conf.
Ahh that would be a bit of a problem. Looks horribly like a rebuild of busybox may be in order to me.
Or perhaps try calling syslogd with the -K option (assuming all the messages are bothering you are comming from the kernel) but then of course that is a bit of a bodge because now you have no kernel logging. The -K option seems to be unique to the busybox version of syslogd BTW
Apologies to any who may have received duplicates of my last message ... a little tangle in sending!
Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 10-May-05 Time: 21:44:25 ------------------------------ XFMail ------------------------------
-
Martijn Koster -
Stuart Bailey -
Ted.Harding＠nessie.mcc.ac.uk -
Wayne Stallwood -
Wayne Stallwood