[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log
Subject:    scheduling (was: multilog pattern)
From:       prj () po ! cwru ! edu (Paul Jarc)
Date:       2001-10-02 16:43:14
[Download RAW message or body]

Mail-Followup-To set.

"clemensF" <rabat@web.de> wrote:
> Paul Jarc:
>> Similar functionality (run a job after every N seconds of service
>> uptime) will be available in future versions of runwhen, after I
>> change things to work with absolute times instead of offsets.  I
>> hadn't planned it, but I think it happens to work out that way.

On further thought, this might not happen.  At least, it won't come
for free like I thought it would.

>> Anacron-like functionality is already available, BTW.

But this is still true; see below.

> does it save execution times somewhere, so that i can have weekly
> jobs even when the system has to go down for maintenance, silence or
> so?

I'm not sure what you mean.  You can schedule a job to run, say,
Sundays at 02:30, and also with the constraint that no more than 7 1/2
days should pass between runs.  If the service (or the whole system)
was down during a scheduled run time, then when it comes back up, the
job will be rescheduled to run 12 hours late (or, if that time is
already past, it will run immediately).  Have a look at the
documentation.


paul

[prev in list] [next in list] [prev in thread] [next in thread]