Timeline for restart systemd service within a timeframe
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 15, 2018 at 11:50 | comment | added | JdeBP | It's not an improvement for the simple reason that it does not actually work. (-: The manual explains why. | |
| Nov 15, 2018 at 4:06 | comment | added | filbranden |
In short, at 08:00 run systemctl --runtime set-property wibble.service Restart=yes and at 17:00 run systemctl --runtime set-property wibble.service Restart=no. At boot, need to run a shell script that will check whether the current hour is in [8, 17) and set it to yes, otherwise to no.
|
|
| Nov 15, 2018 at 4:04 | comment | added | filbranden |
A slight improvement here is to use systemctl set-property, which will essentially do the management of an override for you in a much simpler way. Using --runtime is also possible, since having the overrides in /run is probably OK (boot needs special handling anyway, since there's no guarantee restart will be in the same state at that point.)
|
|
| Nov 14, 2018 at 12:00 | history | answered | JdeBP | CC BY-SA 4.0 |