Re: crontab and editors (was Re: Editor Priorities)
On 09-May-02, 10:10 (CDT), Wichert Akkerman <email@example.com> wrote:
> Attached. The new code creates a temporary directory securely and
> puts a temporary file in there. This is a guaranteed safe procedure
> and allows an editor freedom to create backup files as well.
Thanks. I'll check it and add it to the next unstable upload.
> What someone should really do is compltely rewrite crontab, that
> code is complete horror, especially for something that is suid.
And crontab.c is only the beginning... :-( If you want true horror, try
reading the stuff that parses the file...
Someone should completely rewrite cron...actually, that's been done.
What really needs to be done is a new scheduled job system, with a
reliably parseable file format, so that the alternative front ends may
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com