X-Spam-Check-By: sourceware.org
Message-ID: <43F160B4.E6847F43@dessent.net>
Date: Mon, 13 Feb 2006 20:46:44 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Windows 2000 cron errors
References: <43F15CD6 DOT 3070100 AT comground DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Vince LaMonica wrote:

> 0,5,10,15,20,25,35,40,45,50,55 * * * * [...]

Consider specifying this as "*/5 * * * *" which is more concise and
readable.

> ----------------------------------
> The description for Event ID ( 0 ) in Source ( /USR/SBIN/CRON ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. The following information is part of the event:
> /USR/SBIN/CRON: PID 2292: (Administrator) CMD
> (/home/Administrator/run_cc.sh >> /dev/null 2>&1).
> ----------------------------------

This is just the standard cron syslog output.  You would see the same
thing on any standard unix system, except it would be in /var/log/syslog
(or some other similar file) and it would not contain the boilerplate
spam about not being able to find a description for the event ID. 
Everything up to and including "is part of the event:" is just crap that
Windows adds when there is not a registered message source; the rest of
the message is from cron.  You can actually avoid this with a small
patch to Cygwin DLL's resource file and a few registry entries, but all
that does is remove the extraneous part of the entry: you would still
have the cron output for each job that is run.

What you *can* do is run a syslog daemon, instead of relying on the
behavior that if one is not running the syslog output goes to the Event
Log.  But this just means that you have this output in some file in
/var/log instead of in the Event Log.

Brian

--
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/