Subject: Re: syntax ideas solicited
To: Robert Elz <kre@munnari.OZ.AU>
From: Jarkko Hietaniemi <firstname.lastname@example.org>
Date: 12/25/2001 19:35:57
On Tue, Dec 25, 2001 at 02:52:18PM +0700, Robert Elz wrote:
> Date: 24 Dec 2001 15:25:23 -0500
> From: "Perry E. Metzger" <email@example.com>
> Message-ID: <firstname.lastname@example.org>
> | Any ideas on an appropriate character, or alternate syntaxes, or ideas
> | on prior art, or just plain ideas?
> Please don't start adding funny characters at the start of the line,
> crontab syntax is already foul enough.
> But if you really need this, since cron already supports setting sh type
> variables, why not do something like
> * 0 * * * ...
> <and another>
Hmmm. Why not hide this new magic inside comments?
> to specify the bounds on when the command should be started of the time
> specified (with "WITHIN=0" being the default, and meaning "before time for
> the command to run next" which is what it currently does I believe).
> (The value would be a limit in seconds, allow "5m" and such if you want).
> Personally, I'd be just as happy if cron would simply ignore time jumps
> longer than 5 minutes - run nothing at all that was supposed to happen
Personally, I think Hardwired defaults like this usually end up making
very few people happy.
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen