[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Should packages depend on cron?



On Fri, 25 Jul 1997, Christian Schwarz wrote:

> I've have another idea: I think we only need a solution of how to handle
> /etc/cron.* jobs if the system was not running at about 6:45am (that's
> when the jobs are executed).
> 
> Anacron keeps track of which jobs where executed at which time simply be
> writing a time-stamp into the /var/spool/anacron/* files. So what about
> changing "run-parts" to update these files if "cron" did execute the jobs?
> 
> We could install both, cron and anacron on _every_ system, tell both
> programs to take control over the /etc/cron.* scripts and run anacron at
> boot-up time.
> 
> Systems that are running 24 hours a day will not notice anacron, unless
> they shutdown the system and power it on later, so that the 6:45am jobs
> don't run (in which case anacron will start them at bootup time).
> 
> Systems that are power on and off several times will not notice the "cron"
> jobs, unless the system is running at 6:45am.
> 
> Doesn't this sound like a good solution for everyone?

The only problem I can think of is if someone turns on their computer a
just before cron would normally run a job.  Then you get the job run
twice, but that's no big deal.  I think this will work, except that I
would only have anacron suggested, not required.  Yes there are a few
people who want a bare bones system :-)

Brandon

-----
Brandon Mitchell                         E-mail: bhmit1@mail.wm.edu
  Homepage: http://www.geocities.com/SiliconValley/7877/home.html

"We all know Linux is great...it does infinite loops in 5 seconds."
	--Linus Torvalds


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: