cron on Win9x works

[BB]

"Luciano" <lucianoav@gmx.net> wrote in message
news:Xns935AE4A876607lucianoavgmxnet@80.91.224.249...
> I read it again, but I am not sure I understand it. The hack proposed
> by BB him/herself

him

>
> rm -R -f /var/cron/tabs.sav
> cp -R /var/cron/tabs /var/cron/tabs.sav
> rm -R -f /var/cron/tabs
> mv /var/cron/tabs.sav /var/cron/tabs

cron compares the timestamp of it's 'old' database of tasks to the timestamp
of the /var/corn/tabs directory.  Assuming the all 4 steps (rm, cp, rm, mv)
worked, the newly created /var/cron/tabs should have a new timestamp.  Make
sure it is getting changed to a new time.

If a directory already exists when a mv is done to it, the directory will
not get a new timestamp.  For instance, if for some reason the third step
removing the /var/cron/tabs directory fails, the last step mv will not
update the timestamp.

I would think that this kludge should not be a long term solution.  A change
to cron should fix this problem.

Also, beware that if you are doing the 4 steps and the tabs directory does
not exist when cron checks for it, cron will terminate.

BB

>
> doesn't work here. Cron still skips tasks. I also tried touch'ing the
> tab file, but it didn't work either. Elusive.
>
> Luciano ES
> Santos, SP - Brasil
>
> ********************************
> Igor Pechtchanski <pechtcha@cs.nyu.edu> wrote in
> news:Pine.GSO.4.44.0304112049570.26381-100000@slinky.cs.nyu.edu:
>
> > Please reread the message.  Cron doesn't detect changes to
> > /var/cron/tabs, so you have to make sure the timestamp changes
> > before cron will run new commands.
> >      Igor
>
>




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