| 1 |
On 2017-11-03 18:21, Ian Zimmerman wrote: |
| 2 |
|
| 3 |
> On 2017-11-03 02:53, Kai Peter wrote: |
| 4 |
|
| 5 |
> |
| 6 |
|
| 7 |
>> 2. the shell script have to do some checks, e.g. the last run - I did |
| 8 |
|
| 9 |
>> wrote a small 'include' script for that |
| 10 |
|
| 11 |
> |
| 12 |
|
| 13 |
> Isn't your 'small include script' just another implementation of |
| 14 |
|
| 15 |
> run-crons? |
| 16 |
|
| 17 |
No. |
| 18 |
|
| 19 |
> |
| 20 |
|
| 21 |
> If not: how does it handle _missed_ jobs, if at all? |
| 22 |
|
| 23 |
Whatever _missed_ means - at least it's |
| 24 |
a question of error handling. |
| 25 |
|
| 26 |
> |
| 27 |
|
| 28 |
> If you want to run a monthly job on a host that is not always on, do |
| 29 |
|
| 30 |
> you |
| 31 |
|
| 32 |
> have to pretend it's an hourly job and check in the script itself? |
| 33 |
|
| 34 |
This is a special case to me. IMHO special cases have to be handled |
| 35 |
|
| 36 |
special or much better: avoid it. |
| 37 |
|
| 38 |
> |
| 39 |
|
| 40 |
>> Thus it's portable. The job have to be done once. |
| 41 |
|
| 42 |
> |
| 43 |
|
| 44 |
> If you want your _entire_ configuration to be portable, and my above |
| 45 |
|
| 46 |
> point |
| 47 |
|
| 48 |
> about monthly schedule sticks, then you have to ignore the monthly |
| 49 |
|
| 50 |
> feature of all the crons on all your systems, because you cannot rely |
| 51 |
|
| 52 |
> on |
| 53 |
|
| 54 |
> it in any one system. |
| 55 |
|
| 56 |
My _entire_ config isn't portable, but some |
| 57 |
(important) parts of it. |
| 58 |
|
| 59 |
|
| 60 |
|
| 61 |
-- |
| 62 |
|
| 63 |
Sent with eQmail-1.10 |
Archives