Messages on screen from syslog file

[Marco Camacho_1]

Hi all.

When I start a telnet o secure shell sesion, I receive a lot of messages coming from syslog file. ¿How can i stop this messages on my screen?.

Any help is appreciated. Thanks

[Bill Hassell]

What messages? syslog is just a file. System messages are sent to whatever file (or login) that is specified in /etc/syslog.conf so check there to see why messages are sent from the syslog daemon to your screen.

[Marco Camacho_1]

Hi Bill. It seems any messages who is written in to /var/adm/messages.log or /var/adm/syslog/syslog.log is forward to my screen. is this behavior a parameter on syslog configuration file?

Best Regards.!!

[Steven E. Protter]

Shalom,

It is possible to re-route console output to any terminal device.

check the syslog configuration file (syslog.conf or syslogd.conf).

Check /etc/inttab for strange entries against a system that does not do this.

This is a bit of a detective novel now, but the system has been altered to send console output to a non-standard location. Probably.

If you are logging in to a device that is capable of being a remote console, it may be a problem with the main console causing this.

insf -e might clean up the device files by re-creating them.

SEP

[Scot Bean]

Or you may be using the console. Use a different connection/window.

[Bill Hassell]

> Hi Bill. It seems any messages who is written in to /var/adm/messages.log or /var/adm/syslog/syslog.log is forward to my screen. is this behavior a parameter on syslog configuration file?

Correct. The standard /etc/syslog.conf file only send emergency messages to every logged in user. The relevant entries are:

*.alert /dev/console
*.alert root
*.emerg *

which means that alert messages are sent to the console and wherever root has logged in. All emerg messages are sent to every user on the system. Now if some root user decided to be cute, the following entry:

*.* *

would jam every logged in user with debug messages -- a poor joke. If you want the orioginal syslog.conf, just copy it from /usr/newconfig/etc/syslog.conf to /etc/syslog.conf. The restart syslogd like this:

kill -HUP $(cat /var/run/syslog.pid)

Things will return to normal. Then ask the root user(s) why they changed this file.