| 1 |
On Mon, 2021-12-13 at 22:38 +0100, Frank Steinmetzger wrote: |
| 2 |
> |
| 3 |
> Well I *could* disable run-crons altogether and add entries to fcron’s own |
| 4 |
> crontab which would run those scripts in /etc/cron.{hourly,daily,...} |
| 5 |
> instead. |
| 6 |
> |
| 7 |
> However, I like predictable times at which those jobs will run. Especially |
| 8 |
> if one of them is a zfs scrub; the NAS is powered down for weeks, sometimes |
| 9 |
> months. And when I power it up, it’s for a reason. And that reason usually |
| 10 |
> is not a scrub, which—at the current zfs fill level—takes 10½ hours. |
| 11 |
> |
| 12 |
|
| 13 |
Why choose fcron then? It sounds like you have the same rationale as I |
| 14 |
do: "no, I don't want to run the 4am backup job in the middle of the |
| 15 |
business day just because it wasn't run at 4am." |
| 16 |
|
| 17 |
If you pick a dumber cron, the crontab entries are run only at the |
| 18 |
specified times. |
Archives