Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: Jason Waldhelm Organization: Brundage Management Company, Inc. To: cygwin AT cygwin DOT com Subject: cron problems - no longer functions after changing system date Date: Wed, 12 Feb 2003 16:08:05 -0600 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200302121608.05391.jason@brundagemgt.com> X-Spam-Score: 0.1 (/) X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *18j53u-0007zl-00*ku4p5iGHvs.* hello, I've noticed a problem with the cron service and as of yet, haven't found any posts that echo my problem. It seems whenever the system date is changed on the computer on which cron is running as a service, the cron daemon stops functioning. The service itself doesn't appear to stop (Windows 2000 Server reports it as running), but all jobs scheduled to run via cron cease functioning after the date is changed. I've managed to work around this problem scheduling cron restart jobs via the Windows Task Scheduler, but it is still a nuisance. I've also used the cron testing script provided on your site to make sure that cron and all directories, etc. are setup properly - the script seems to think everything is fine. Given that my jobs run normally as expected when the date isn't changed, it leads me to believe it is a cron-related problem. Has I'm running Windows 2000 Server, SP3 cygwin-1.3.17-1 cron-3.0.1-7 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/