From owner-freebsd-security Mon Jan 28 7:20:38 2002 Delivered-To: freebsd-security@freebsd.org Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by hub.freebsd.org (Postfix) with ESMTP id D6BF437B404 for ; Mon, 28 Jan 2002 07:20:35 -0800 (PST) Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.11.6/8.11.3) with ESMTP id g0SFKZM99969 for ; Mon, 28 Jan 2002 09:20:35 -0600 (CST) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200201281520.g0SFKZM99969@dc.cis.okstate.edu> To: freebsd-security@freebsd.org Subject: Controlling Cron Logging Date: Mon, 28 Jan 2002 09:20:35 -0600 From: Martin McCormick Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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? Cron is chatty enough that I would like to confine its reports every minute on the minute to one file. Thank you Martin McCormick OSU Center for Computing and Information services Network Operations Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message