X-Spam-Check-By:	sourceware.org
Date:	Wed, 18 Jan 2006 16:59:53 -0500 (EST)
From:	Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Herman Poon <poonh AT mcmaster DOT ca>
cc:	cygwin AT cygwin DOT com
Subject:	Re: cron - Application Event Log
In-Reply-To:	<web-115144259@cgpsrv2.cis.mcmaster.ca>
Message-ID:	<Pine.GSO.4.63.0601181644520.20867@access1.cims.nyu.edu>
References:	<web-115144259 AT cgpsrv2 DOT cis DOT mcmaster DOT ca>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Wed, 18 Jan 2006, Herman Poon wrote:

> I would like to suppress logging of tasks by cron in the Windows
> Application Event log. I want to schedule a task that runs frequently
> but do not want the Event log to quickly grow.
>
> I did search the Cygwin mailing list archive and found this:
> http://sourceware.org/ml/cygwin/2004-10/msg01333.html
>
> I found that the -1 and -2 switches create String values "StdOut" and
> "StdErr" for the Parameters key of the cron service in the registry. It
> would appear that any output should be logged to /var/log/cron.log.
>
> Unfortunately, this does not seem to work and every time a task runs in
> cron, an entry is added to the Application Event log. The cron.log file
> itself only shows lines similar to the following:
> [2252] cron started
>
> The cron.log file doesn't contain anything else, just the pid and the
> "started" line (when cron is stopped it doesn't log anything to
> cron.log). I did stop/restart cron just to see if the settings would
> take effect, but this didn't work either.
>
> I'm hoping that somebody has some suggestions for me. Thank you,

Cron uses the syslog interface to log its events.  By default, syslog
messages go to the Event log, unless you run the syslogd daemon.  You
should be able to install syslogd as a service using the
/bin/syslogd-config script, and then control it using /etc/syslogd.conf.
Enjoy,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -