This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cron malfunction after date change
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 5 Nov 2004 11:38:24 -0500
- Subject: Re: Cron malfunction after date change
- References: <BADF3C947A1BD54FBA75C70C241B0B9E90BD28@ex02.svr.idirect.net>
- Reply-to: cygwin at cygwin dot com
On Fri, Nov 05, 2004 at 11:26:05AM -0500, Harig, Mark wrote:
>>cron.log, crontab.txt and cygcheck.txt attached. Stopping and starting
>>cron is workaround that does resume correct cron behaviour, up until
>>next date change. I've been able to reproduce this
>>(http://cygwin.com/ml/cygwin/2004-11/msg00153.html) problem also on
>>WinXP with slightly older cygwin1.dll version:
>>1.5.11-snapshot-20040720-12:03:09.
>>
>
>I concur. It appears to be a bug in cron, or Cygwin's version of cron.
Can anyone point to some documentation which states that cron is
supposed to gracefully handle date changes? Personally, I've always
restarted cron after a date change since I've noticed behavior like this
on linux in the past. If that has been fixed, however, that would be an
interesting data point for linux (off-topic) and cygwin (on-topic).
cgf
--
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/