Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!oliveb!amiga!boing!dale
From: dale@boing.UUCP (Dale Luck)
Newsgroups: comp.sys.amiga
Subject: Re: DCRON
Message-ID: <548@boing.UUCP>
Date: 27 Dec 88 16:31:32 GMT
References: <8812230336.AA06015@postgres.Berkeley.EDU> <1176@dukeac.UUCP>
Reply-To: dale@boing.UUCP (Dale Luck)
Organization: Boing, Milpitas, Ca.
Lines: 14

In article <1176@dukeac.UUCP> rsb@dukeac.UUCP (R. Scott Bartlett) writes:
>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).

Not really knowing how arex works, maybe this would solve the problem.

Maybe put an arex port in the dameon, send an arex command to it after
editing the crontab, telling it to reread the crontab file.
-- 
Dale Luck     GfxBase/Boing, Inc.
{uunet!cbmvax|pyramid}!amiga!boing!dale