Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

Tue Jan 23 04:26:00 GMT 2007

>Date: 2007年1月22日 15:16:19 -0800
>From: Brian Dessent <brian at dessent dot net>
>>Steve Rowley wrote:
>> >In case of problem, examine the log file for cron,
>> >/var/log/cron.log, and the Windows event log
>> >for information about the problem cron is having.
>>This is the key thing to look at, the actual reason for why it can't
>start should be in one of those two locations.

Excellent points. Here are the results:
(1) There is no /var/log/cron.log. Since this is the first time I've
 tried to bring up cron on this machine, I take it to indicate that
 the daemon never got as far as creating its log file.
(2) Windows event log: yes, there are some cron-related events there.
 Had I read the message as carefully as you did, I would have
 found Application events like this:
 >Event Type:	Error
 >Event Source:	cron
 >Event Category:	None
 >Event ID:	0
 >Date:		1/22/2007
 >Time:		11:00:27 PM
 >User:		NT AUTHORITY\SYSTEM
 >Computer:	CBDWB00033
 >Description:
 >The description for Event ID ( 0 ) in Source ( 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: cron: PID 304: starting service `cron' failed: fork: 11, Resource temporarily unavailable.
Any idea what to make of that?
>> >/usr/bin/cygrunsrv: Error enumerating services: OpenService: Win32 error 5:
>> >Access is denied.
>>This usually just means there's a registry key for a service that has an
>ACL that returns an error when cygrunsrv tries to query its information
>to find out if it's a Cygwin service. Most of the time this can be
>ignored [...]

Good, then we'll all happily ignore it.
>> [ATTACHMENT ~/My Documents/cygcheck_output.txt, text/plain]
>>You didn't actually attach anything, just this text.

Silly me. I actually understand why that happened, but won't bore you
with the reason, unless I can think of an entertaining way to tell it.
In any case, I've reattached the output of cygchek to this message.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygcheck_output.txt
URL: <http://cygwin.com/pipermail/cygwin/attachments/20070123/5ffcaca4/attachment.txt>
-------------- next part --------------
-- 
Steve Rowley <sgr@alum.mit.edu> http://alum.mit.edu/www/sgr/ Skype: sgr000
It is very dark & after 2000. If you continue, you are likely to be eaten by a bleen.
-------------- next part --------------
--
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/