error messages output to screen

[ivychung2]

I use telnet to access to the RH server , now I found that some error messages output to my screen , I also found the same error message in /var/log/messages ( this kind of messages should be in here ) , so I am wonder why this message will send to my telnet session , I have checked the setting file under /etc/ , /var/ , it seems no any config file related to it , could suggest what is wrong ? thx

[Muthukumar_5]

what is there in /etc/syslog.conf on related with console keyword. It will send error messages to your console.

--
Muthu

[ivychung2]

thx reply
I hv check it , the conf file seems normal , is there other conf file related to it ? thx

[Ivan Ferreira]

Post your syslog.conf file, is the only file related to system logging. If you find a destination of "*", this may be causing the message appearing to your screen.

[ivychung2]

thx reply ,

in /etc/syslog.conf , the below is the setting, thx


# The authpriv file has restricted access.
authpriv.* /var/log/secure

# Log all the mail messages in one place.
mail.* /var/log/maillog


# Log cron stuff
cron.* /var/log/cron

# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler

# Save boot messages also to boot.log
local7.* /var/log/boot.log

[Stuart Browne]

Odd. What sort of error messages are you getting to your telnet session?

As Ivan mentioned, a target of * would go to your a console. On most RH boxes, there is a line in syslog.conf that looks like:

# Everybody gets emergency messages
*.emerg *

This simply states that any emergency log messages go to every-open-tty (i.e. your telnet session as well as everybody elses).

Otherwise, people can send messages to your tty directly if they have write access to the /dev/tty* nodes, or it's not the RH box spitting out the error (which is why I asked for an example of the message).

[ivychung2]

thx reply,

In the setting file , the statement " # Everybody gets emergency messages
*.emerg * " is present but I have disable it already ,

the messages likes :
nfs: RPC call returned error 101

smb_get_length: recv error = 5
smb_trans2_request: result=-5, setting invalid
smb_lookup: find //stamp failed, error=-5
smb_lookup: find //stamp failed, error=-5
smb_lookup: find //stamp failed, error=-5
smb_lookup: find //stamp failed, error=-5

[Stuart Browne]

I get the samba ones too (but that's on a Fedora Core 1 box). It's part of the samba code base. Just make sure you've got the latest update of Samba.

As for the NFS one, that's odd. But I'll say the same thing. The portmap, as well as kernel and nfs packages should be at the latest version.