home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!destroyer!gumby!wupost!cs.utexas.edu!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!mcdchg!laidbak!tellab5!obdient!homer!eternal!jgostin
- From: jgostin@eternal.chi.il.us (Jeff Gostin)
- Newsgroups: comp.bbs.waffle
- Subject: Re: Waffle Scheduler
- Message-ID: <ui8euB1w165w@eternal.chi.il.us>
- Date: 18 Nov 92 05:52:53 GMT
- References: <6R4BuB1w165w@cuckoo.egg.com>
- Organization: The little node that could...
- Lines: 29
-
- tomg@cuckoo.egg.com (Grand Master) writes:
-
- > Did anyone figure out what the anomally is with the scheduler?
- >
- > Mine (v1.65) was chugging along happily for a couple of months doing its
- > appointed tasks at its appointed time. Yesterday at 10:00am it decided to
- > quit. It stopped calling out for no apparent reason. Absolutely nothing
- > was changed in the system. I'm baffled and Waffled!
- >
- > Any ideas?
-
- Sure do.... :-) Check the date/time of ~/system/stamp. I will bet
- dollars to donuts that it's probably set a tad bazarrely, IE: It shouldnt
- be the time/date it is. Allow me to explain. When Waffle runs a scheduled
- job, it updates the time/date stamp of the ~/system/stamp file. This is
- how waffle knows what has and hasnt been executed. If the date is wrong,
- it won't execute until that date has passed. I've seen it happen here... I
- accidently set the date to xx/xx/*93*, and couldnt imagine why no jobs
- were being executed. I corrected the date, and voila, it worked.
-
-
- Jeff
-
- ...From a tiny little node called Eternal!
- --
- /|Email to: jgostin@eternal.chi.il.us, offline@infopls.chi.il.us
- / |Smail to: Jeff Gostin, 917 High Ridge Pass, Carol Stream IL 60188
- \ |Vmail to: 708-293-5526
- \|Flames to: trashcan@eternal.chi.il.us
-