[despammed] Re: Error messages to console

[Toby Johnson]

I had tried that as well. I don't see anything that would send it to the
screen. In fact, I stopped syslogd once and still got the messages. They
even show up on the console when no one is logged in there; it's just
sitting at the login prompt.

Here is my syslog.conf, in case you see anything I don't. The "Bastille"
stuff is from the Bastille Firewall for RedHat:

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none                /var/log/messages

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

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

daemon.*                                                /var/log/daemon

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

# Everybody gets emergency messages
*.emerg                                                 *

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

# Save boot messages also to boot.log
local7.*                                                /var/log/boot.log
############ BASTILLE ADDITIONS BELOW : #################
# Log warning and errors to the new file /var/log/syslog
*.warn;*.err    /var/log/syslog

# Log all kernel messages to the new file /var/log/kernel
kern.*  /var/log/kernel

# Log all logins to /var/log/loginlog
auth.*;user.*;daemon.none       /var/log/loginlog

########## BASTILLE ADDITIONS CONCLUDED : ###############



Bill Moran said:
> Check your syslog.conf (usually in /etc)
> It will generally control where certain messages go to.  Look for lines
> that log to the console, or lines that log to "root".  These will show
> up on your console if you're logged in as root.  Tweak them to stop the
> console messges.
>
> On Friday 19 October 2001 01:29, public at tobiasly.com wrote:
>> These messages are coming from smbmount sessions I have active. I
>> guess that means I start them from the console using 'mount'. So how
>> do I prevent this? I even changed /sbin/mount.smb to a script that
>> calls "/usr/bin/smbmount <options> >/dev/null 2>&1" and still the
>> messages appear.
>>
>> The smbd and nmbd daemons were started from their respective init.d
>> scripts.
>>
>> Ian Cooper said:
>> > If you have started the smbd and nmbd daemons from the
>> > console, then messages may get sent there.
>> >
>> > --
>> > Ian Cooper
>> > ian at wpi.edu
>> >
>> > On Wed, 17 Oct 2001, Toby Johnson wrote:
>> > > Date: Wed, 17 Oct 2001 00:24:01 -0400
>> > > From: Toby Johnson <toby at tobiasly.com>
>> > > To: samba at lists.samba.org
>> > > Subject: Error messages to console
>> > >
>> > > I have seen lots of posts regarding the "smb_retry"
>> >
>> > messages but none
>> >
>> > > addressing why they would go to the console as well as the
>> >
>> > log files.
>> >
>> > > For some reason these messages always are copied to my
>> >
>> > screen. How can
>> >
>> > > I prevent this?
>> > >
>> > > Example messages:
>> > > smb_trans2_request: result=-104, setting invalid
>> > > smb_retry: successful, new pid=27062, generation=6
>> > >
>> > > tia,
>> > > toby
>> > >
>> > >
>> > > --
>> > > To unsubscribe from this list go to the following URL and read the
>> > > instructions:  http://lists.samba.org/mailman/listinfo/samba
>
> --
> Bill Moran
> Potential Technology technical services
> (412) 793-4257
>
> ----------------------------------------------
> Filtered by despammed.com.  Tracer: JAA021281003501324
> Despammed.com now has user services!  Change your password or
> forwarding address at: http://www.despammed.com/despammed/user