On 9/15/24 12:30, Andrew via austin-group-l at The Open Group wrote:
Also, the contents of -e are relative to the user privilege context (root/sudo
vs non-root user). That is more accident prone than direct text files, which
tend to be housed in directories that convey more context about job ownership (/
etc vs $HOME).
One common extension that hasn't made it into the standards is to allow
specifying the username on the command line - though the standard says it
only covers usage by "users with normal privileges", who normally wouldn't
be able to control jobs for other users.
Allow cron configuration files to have a (.cron) file extension. This helps text
editors and linters to correctly identify cron job configuration files, without
having to resort to modeline tricks.
The standard says nothing about what filename crontab passes to the editor - an
implementation could certainly apply a .cron suffix to their temporary file
name.
While I would heartily recommend a cloud scheduler such as Google Cloud for many
kinds of tasks, there are still many uses for humble cron, and so I think it
deserves some more polish.
The standard only requires crontab, not a cron daemon - crontab could submit the
jobs to another scheduler or service manager, such as systemd, SMF, etc.
Regardless, less than (<), less than or equal to (<=), greater
than (<), and greater than or equal to (>=) would be a more intuitive syntax.
And far harder to use, with most shells interpreting < and > as input and output
redirections, requiring users to have to escape them to use them with find.
--
-Alan Coopersmith- [email protected]
Oracle Solaris Engineering - https://blogs.oracle.com/solaris
