From owner-freebsd-security  Mon Jan 28  9:43:34 2002
Delivered-To: freebsd-security@freebsd.org
Received: from upeople.iserver.net (upeople.iserver.net [128.121.116.62])
	by hub.freebsd.org (Postfix) with ESMTP id 871F137B417
	for <freebsd-security@FreeBSD.ORG>; Mon, 28 Jan 2002 09:43:28 -0800 (PST)
Received: from mesa.unixan.com (djb@mesa.dsl.unixan.com [206.124.137.18]) by upeople.iserver.net (8.11.6) id g0SHhRN35468; Mon, 28 Jan 2002 10:43:27 -0700 (MST)
Date: Mon, 28 Jan 2002 09:43:23 -0800
From: Daniel Brown <djb@unixan.com>
To: freebsd-security@FreeBSD.ORG
Cc: martin@dc.cis.okstate.edu
Subject: Re: Controlling Cron Logging
Message-Id: <20020128094323.5e3a6768.djb@unixan.com>
In-Reply-To: <20020128102745.J454@yip.org>
References: <200201281520.g0SFKZM99969@dc.cis.okstate.edu>
	<20020128102745.J454@yip.org>
X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Face: ".E)>Dp:mH<OtVR$Zb)eCw;6LEM[iZr4],$RT.#eYE/LB{@vq?x2QV}zd{cIx$]:g!uKx$Nr/mgHeM'CVI?=_m$vhe>JC%;_j&|O(iET^Y#v)'R,3Th)?un#2[`x7J&@ClPD0?MlzHBP61gci=t1G!Jf8V9r+nMFv:GX&}5R2YZ@lzKO_S5,^.!^<^OijwA[0*`cfC'.Ft7-qcuK4^-Cu
X-Frustrated-Since: 999302400
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-security.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-security>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-security>
X-Loop: FreeBSD.org

It may not be wise to entirely remove cron from /var/log/syslog.  If
something serious occurs and cron complains about it, generally it
should still be logged to /var/log/syslog so it will not be overlooked.

Try:

*.info;auth.info;mail.warning;cron.warning	/var/log/syslog

      -Daniel

------------ Quoted Message ------------
Date...: Mon, 28 Jan 2002 10:27:45 -0500
From...: Bob K <melange@yip.org>
To.....: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Re: Controlling Cron Logging

On Mon, Jan 28, 2002 at 09:20:35AM -0600, Martin McCormick wrote:
> 	I have a syslog file which is set up to log as follows:
> 
> *.info;auth.info;mail.warning		/var/log/syslog
> 
> 	That appears to work well.  Now, I wanted to refine
> things a bit and not see cron logging there so I uncommented the
> line in /etc/syslog.conf which now looks like:
> 
> cron.*						/var/log/cron
> 
> 	That now sends the cron messages to the file
> /var/log/cron like it should.  Is there any way I can cause the
> cron messages to stop going to syslog while leaving it wide open
> for anything but cron?

Changing this line:

> *.info;auth.info;mail.warning		/var/log/syslog

so it looks like this:

> *.info;auth.info;mail.warning;cron.none	/var/log/syslog

should, in theory, have the effect you seek.

-- 
Bob <melange@yip.org> | Please don't feed the sock puppet.

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



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