Thank god it's not all that obvious (as this thread implies), because when I first started to look at the cron and andcron man pages, I didn't really know where to start.
I've set up a crontab entry in /etc/cron.d for my script, which I guess it the right way to go. I didn't use Kcron, which I didn't know about when I started. Chris On Friday 03 October 2003 04:22, Bijan Soleymani wrote: > On Fri, Oct 03, 2003 at 01:04:04AM +0100, Pigeon wrote: > > On Wed, Oct 01, 2003 at 07:55:30PM -0700, Paul Johnson wrote: > > > On Wed, Oct 01, 2003 at 12:15:19PM -0400, Derrick 'dman' Hudson wrote: > > > > anacron. > > > > > > > > cron and anacron solve similar problems but with a different approach > > > > based on different requirements. The two are not mutually exclusive. > > > > > > Ah. Well, that's for stuff that has to be run even when the machine's > > > down. > > > > I'd love to be able to run stuff when my machine's down. :-) What did > > you actually mean? > > I don't know what he meant but the way I understand it, cron runs stuff > at a specified time. For example you could set up logrotation to happen > on tuesdays at 11:05 PM. Except what happens if the user turns off the > machine at 10 oclock each night. Then the logs never get rotated. With > anacron you say the logrotation should occur every X hours/days/etc the > computer is on. > > P.S. I'm really not sure about this, I've never used anachron directly, > though I have used cron a good deal. > > Bijan -- Dr.-Ing. Christof Hurschler Bodenstedtstr. 13 D-30173 Hannover +49-0172-5946909 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
