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
Date:	Fri, 5 Nov 2004 11:38:24 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cron malfunction after date change
Message-ID:	<20041105163824.GI18823@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<BADF3C947A1BD54FBA75C70C241B0B9E90BD28 AT ex02 DOT svr DOT idirect DOT net>
Mime-Version:	1.0
In-Reply-To:	<BADF3C947A1BD54FBA75C70C241B0B9E90BD28@ex02.svr.idirect.net>
User-Agent:	Mutt/1.4.1i

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/

- Raw text -