Path: utzoo!attcan!uunet!husc6!rutgers!mcnc!ecsvax!dukeac!rsb
From: rsb@dukeac.UUCP (R. Scott Bartlett)
Newsgroups: comp.sys.amiga
Subject: Re: DCRON
Message-ID: <1176@dukeac.UUCP>
Date: 23 Dec 88 15:10:10 GMT
References: <8812230336.AA06015@postgres.Berkeley.EDU>
Reply-To: rsb@dukeac.UUCP (R. Scott Bartlett)
Organization: Center for Demographic Studies, Duke University, Durham, NC
Lines: 24
Summary:

In article <8812230336.AA06015@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
>  The major feature is that it does not scan the file every minute,
>but calculates how long it must wait till the next scan.
	This doesn't allow one to modify the crontab file and expect cron to
pick up on the changes immediately (well, a minute later).  With DCRON, if you
modify the crontab, DCRON won't realize the change untill it has to do something
from the old crontab.  I don't mind AmiCron polling the disk every minute at
all; in fact, i use this feature to my advantage to know when the HD buffers
have been flushed so that i can reboot (but that's beside the point).

>(A further refinement
>would be to read in the file into memory and not scan it at all from disk
>unless it was modified, but unless you do something every minute the extra
>memory taken up may not be worth it).
I think that this might be worth it, in some form or another.

						rsb


-- 
rsb@dukeac.ac.duke.edu		///	"Amigas do it with hardware."-- Me
rutgers!mcnc!ecsvax!dukeac!rsb ///     "Sycamore is open."-- Negativ Land
I'm a HORSE, of course.    \\\///     "I luv S&M!!!"   "No geeks here!!"
Disclaimer NOT included!    \XX/     "This space for rent"