RE: Cron malfunction after date change

2004-11-08 Thread Harig, Mark
> 
> >>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).
> 

The original problem ("cron is not running over the course of a 
24-hour date change") is not a Cygwin-specific problem, i.e., Cygwin's 
cron appears to work when asked to perform a task once a day at a
specified time.  I wrote a simple cron table entry

   1 1 * * * /usr/bin/date >> /tmp/date.txt

'cron' ran this task for me for the past three days without errors
or intervention.

I do not know whether the secondary problem ("cron fails to run
without a restart if there has been a date change outside of the 
normal clock") is cron specific or Cygwin specific.

---

--
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/



Re: Cron malfunction after date change

2004-11-08 Thread Jacek Trzmiel

Xavier Nodet wrote:
> On Thu, 04 Nov 2004 15:37:12 +0100 Jacek Trzmiel wrote:
> > cygwin1.dll 1.5.11-1, win2ksp4+patches
> 
> Cron is a separate package, that was updated on 20th, October, to
> correct a problem where cron would endlessly sleep after a time/date
> change. Do you have the latest version?

Yes.

$ cygcheck -srv | grep cron
cron3.0.1-13

$ ll /usr/sbin/ | grep cron
-rwxrwxrwx1 sc0rpUsers   25088 Oct 20 14:07 cron.exe

-- Jacek.

--
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/



Re: Cron malfunction after date change

2004-11-08 Thread Xavier Nodet
On Fri, 5 Nov 2004 11:38:24 -0500 Christopher Faylor <[EMAIL PROTECTED]> wrote:

> Personally, I've always restarted cron after a date change

There exist a version of Cron that is supposed to handle date changes.
See
  

-- 
Xavier Nodet
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." - Benjamin Franklin, 1759.


--
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/



Re: Cron malfunction after date change

2004-11-08 Thread Xavier Nodet
On Thu, 04 Nov 2004 15:37:12 +0100 Jacek Trzmiel <[EMAIL PROTECTED]> wrote:

> cygwin1.dll 1.5.11-1, win2ksp4+patches

Cron is a separate package, that was updated on 20th, October, to
correct a problem where cron would endlessly sleep after a time/date
change. Do you have the latest version?

-- 
Xavier Nodet
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." - Benjamin Franklin, 1759.


--
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/



Re: Cron malfunction after date change

2004-11-05 Thread Christopher Faylor
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/



RE: Cron malfunction after date change

2004-11-05 Thread Harig, Mark
> 
> 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.

The following fails to work correctly for me:

1. Create the following crontab entry:

* * * * * /usr/bin/date >> /tmp/date.txt

2. Start cron as a service and wait one minute.  Cron adds a line
to /tmp/date.txt.

3. Using Windows's "Adjust Date/Time" applet, set the date to the previous
day.

4. Wait one minute, and cron adds another line to /tmp/date.txt.

5. Using Windows's "Adjust Date/Time" applet, set the date to the current
day.

6. Wait one (or more) minute, and cron does NOT add another line to /tmp/date.txt.

Cron should resume updating /tmp/date.txt.

If I stop the cron service and restart it, then cron resumes updating /tmp/date.txt.

---

--
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/



RE: Cron malfunction after date change

2004-11-04 Thread Harig, Mark

Please run this diagnostic script.  It will attempt to locate
many types of common problems with cron on cygwin.

http://sources.redhat.com/ml/cygwin/2004-07/msg00207.html

Please read the output of the script carefully.  If it finds
problems, it suggests possible fixes, and it will also recommend
steps to take if it is unable to detect any problems



P.S., Please reply directly to this mailing list and not to me.
Also, please do not include my email address in the reply.


--
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/



Cron malfunction after date change

2004-11-04 Thread Jacek Trzmiel

cygwin1.dll 1.5.11-1, win2ksp4+patches

Steps to reproduce:
1. Start cron:
cygrunsrv --stop cron
cygrunsrv --remove cron
cygrunsrv --install cron -p /usr/sbin/cron -a -D -i
cygrunsrv --start cron

2. Add task to cron to start at specified time (about 3 minutes from
now) every day.  I.e. something like this:
34 15 * * * /some/app

3. Change date to previous day.

4. Wait over a minute.

5. Change date to current day.

6. Wait till time set in step 2.

BUG: Added task doesn't get executed.

EXPECTED: Task started at correct time.


I've also seen something like this:
- I've added task to execute 22:30 every day.
- About 15:00 changed date to previous day, and few minutes later to
current day.
- Task has not been started at 22:30.
- Task has been stated some time after 15:00 next day.

-- Jacek.

--
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/