Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Feb 1999 23:57:25 -0500 (EST)
From:      "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com>
To:        patseal@hyperhost.net (Patrick Seal)
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: syslog.conf
Message-ID:  <199902220457.XAA18436@cc942873-a.ewndsr1.nj.home.com>
In-Reply-To: <Pine.BSF.4.05.9902211554000.37743-100000@foobar.hyperhost.net> from Patrick Seal at "Feb 21, 99 04:11:23 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
Since no one has tackled this yet...

Patrick Seal wrote,
> I'm trying to restrict the messeges that fill up my messeges log file into
> a sudo log. This is what I have so far:
> 
> *.notice;kern.debug;mail.crit                   /var/log/messages
> 
> !sudo
> *.*                             /var/log/sudo
> 
> But sudo stuff still goes into messeges as well as sudo.  How can I
> restrict sudo stuff from the messeges file? I've tried sudo.none but that
> doesn't seem to help, and the man page isn't much help either.

I am not completely familiar with 'sudo,' but my _guess_ is that sudo
messages are part of the 'auth' or 'authpriv' facilities. The
'*.notice' entry is probably what is routing all of those messages to
/var/log/messages. To stop all sudo messages from going to messages,
add 'auth.none' to the end of the list. To direct them as you want,

auth.*						  /var/log/sudo

Now, again, I am not sure how sudo has logging built into it. But this
is a guess and a little more info on syslog.conf. See, 'man
syslog.conf.' In fact, the example on the manpage talks about doing
'authpriv' in a special way.
-- 
Crist J. Clark                           cjclark@home.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902220457.XAA18436>