Mail Archives: cygwin/2003/04/15/11:04:12
"Igor Pechtchanski" <pechtcha AT cs DOT nyu DOT edu> wrote in message
news:Pine DOT GSO DOT 4 DOT 44 DOT 0304151022440 DOT 26381-100000 AT slinky DOT cs DOT nyu DOT edu...
> Reply inline below:
>
> On Tue, 15 Apr 2003, BB wrote:
>
> > "Luciano" <lucianoav AT gmx DOT net> wrote in message
> > news:Xns935AE4A876607lucianoavgmxnet AT 80 DOT 91 DOT 224 DOT 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
>
> BTW, is there a particular reason why you can't do it in 3 steps:
> rm -Rf /var/cron/tabs.sav
> mv /var/cron/tabs /var/cron/tabs.sav
> cp -R /var/cron/tabs.sav /var/cron/tabs
> ?
> Igor
I just wanted to keep the interval that tabs does not exist to a minimum
because cron
will exit if it doesn't find it. I thought the rm and mv might be fast
operations compared
to the cp if there are a lot of tabs. This might even be better so a copy
of tabs gets
saved as a backup. Keep in mind that I'm running on slow Win95 machines.
rm -Rf /var/cron/tabs.tmp
rm -Rf /var/cron/tabs.bak
cp -R /var/cron/tabs /var/cron/tabs.tmp
mv /var/cron/tabs /var/cron/tabs.bak
mv /var/cron/tabs.tmp /var/cron/tabs
Regardless, I think cron should be modified instead of using this long term.
BB
>
> > 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 AT cs DOT nyu DOT edu> wrote in
> > > news:Pine DOT GSO DOT 4 DOT 44 DOT 0304112049570 DOT 26381-100000 AT slinky DOT cs DOT nyu DOT 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
>
> --
> http://cs.nyu.edu/~pechtcha/
> |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu
> ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com
> |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
> '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
>
> Knowledge is an unending adventure at the edge of uncertainty.
> -- Leto II
>
>
--
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/
- Raw text -