| 1 |
On Sun, Nov 5, 2017 at 6:43 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> |
| 3 |
> There are other schedulers out there that succeed where cron fails (eg |
| 4 |
> Control-M, chronos, quartz), but those are all large, bulky, designed |
| 5 |
> for big complex installs/requirements and probably not suited for simple |
| 6 |
> things you'd deploy out of a base in portage |
| 7 |
> |
| 8 |
|
| 9 |
Amusing that you classify 99.999% of all desktop installs as "big |
| 10 |
complex installs." |
| 11 |
|
| 12 |
But, I agree that it makes far more sense to just have desktop users |
| 13 |
use an appropriate cron implementation designed to handle the machine |
| 14 |
being off most of the time vs trying to use shell scripting to make |
| 15 |
vixie cron into such an implementation. |
| 16 |
|
| 17 |
FWIW this is probably the reasoning behind including cron-like |
| 18 |
functionality in systemd, and having it support optionally running |
| 19 |
jobs if the system was down during a calendar-based event. It was |
| 20 |
considered bare-bones functionality that any desktop or generic server |
| 21 |
would need. It is, of course, optional, and just about any kind of |
| 22 |
rule is supported. I personally use systemd-cron which basically is a |
| 23 |
wrapper+generator around /etc/crontab and the various /etc/cron.*/ |
| 24 |
scripts. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Rich |
Archives