Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 5 Nov 2004 11:38:24 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Cron malfunction after date change Message-ID: <20041105163824.GI18823@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/