On Sun, Nov 5, 2017 at 6:43 AM, Alan McKinnon <alan.mckin...@gmail.com> wrote:
>
> There are other schedulers out there that succeed where cron fails (eg
> Control-M, chronos, quartz), but those are all large, bulky, designed
> for big complex installs/requirements and probably not suited for simple
> things you'd deploy out of a base in portage
>

Amusing that you classify 99.999% of all desktop installs as "big
complex installs."

But, I agree that it makes far more sense to just have desktop users
use an appropriate cron implementation designed to handle the machine
being off most of the time vs trying to use shell scripting to make
vixie cron into such an implementation.

FWIW this is probably the reasoning behind including cron-like
functionality in systemd, and having it support optionally running
jobs if the system was down during a calendar-based event.  It was
considered bare-bones functionality that any desktop or generic server
would need.  It is, of course, optional, and just about any kind of
rule is supported.  I personally use systemd-cron which basically is a
wrapper+generator around /etc/crontab and the various /etc/cron.*/
scripts.


-- 
Rich

Reply via email to