Will cron runnnnig as a service cause the server to lock up?
Thu Aug 26 17:41:00 GMT 2010
I'm getting this message in the Event Log for cron kicking off...
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. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information
is part of the event: /usr/sbin/cron: PID 2160: (Administrator) CMD
Does it mean anything?
Thanks for your time and assistance...
Larry Hall (Cygwin) wrote:
> On 8/26/2010 12:59 PM, Blaine Miller wrote:
>> I'm running cron as a service. Twice this week this server has died
>> and needed
>> cold rebooting to get the system back.
>> Questions - First, will cron as a service on a Windows 2003 R2, standard
>> system cause this sort of behavior?
> No, that's an O/S issue (kernel or drivers).
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin