| 1 |
On Sun, Mar 1, 2015 at 7:48 AM, Marc Joliet <marcec@×××.de> wrote: |
| 2 |
> |
| 3 |
> The problem with conditions (as they exist in systemd currently) is the same as |
| 4 |
> with dependencies: the unit does not wait until the condition is met, but |
| 5 |
> immediately stops (only that it doesn't enter a failed state). I mean, this is |
| 6 |
> what conditions in systemd are *supposed* to do, and they do they're |
| 7 |
> designated job, but I would like the timer to wait until the condition is met |
| 8 |
> and *then* run the job. I.e., I want a *delay*. |
| 9 |
|
| 10 |
The timer keeps running if you set the dependency on the service. So, |
| 11 |
next time the timer runs, it will try again. You might want to just |
| 12 |
set an hourly job and have it check for a successful run in the last |
| 13 |
day or whatever. |
| 14 |
|
| 15 |
I don't know if restart=on-failure or on-abnormal applies if the |
| 16 |
service fails to run in the first place. You might try setting that |
| 17 |
with a suitable restartsec=### setting. That might be a better way to |
| 18 |
get the behavior you want if it works. |
| 19 |
|
| 20 |
-- |
| 21 |
Rich |
Archives