Files
systemd/man
Mike Yuan 406aeb5da6 core/service: introduce sd_notify() RESTART_RESET=1 for resetting restart counter
We have RestartMaxDelaySec= + RestartSteps= to exponentially increase
auto restart durations, but it currently cannot be reset by the service
itself, which makes it sometimes awkward to use. A typical pattern
in real life is that a service was once down (e.g. due to temporary
network interruption) and multiple restarts were attempted. Then,
future restarts would always wait for increated amount of time based on
RestartMaxDelaySec=, even after the original problem got resolved.
Such "persistence" could result in longer unavailablity than there
should be for failures that come later.
(C.f. https://utcc.utoronto.ca/~cks/space/blog/linux/SystemdResettingUnitBackoff)

Let's introduce a new sd_notify() notification for resetting the restart
counter. There were discussions about making this timer-based, but I think
it's more flexible to leave the decision-making to the service. This enables
them to do a combination of N successful requests + uptime check for instance.
2025-03-11 00:44:44 +01:00
..
2024-12-25 17:00:31 +01:00
2023-12-25 09:15:53 +01:00
2024-11-24 01:11:42 +09:00
2024-12-25 17:00:31 +01:00
2025-01-28 03:28:26 +09:00
2024-12-25 17:00:31 +01:00
2024-12-25 17:00:31 +01:00
2024-12-25 17:00:31 +01:00
2024-12-25 17:00:31 +01:00
2024-12-25 17:00:31 +01:00
2024-11-06 19:06:47 +09:00
2024-12-25 17:00:31 +01:00
2023-12-26 08:59:53 +01:00
2023-12-26 08:59:53 +01:00
2025-01-28 03:28:26 +09:00
2024-11-24 01:11:42 +09:00
2023-12-26 13:10:36 +01:00
2024-11-24 01:11:42 +09:00
2025-02-27 13:37:20 +09:00
2024-11-24 01:11:42 +09:00
2024-11-24 01:11:42 +09:00
2023-12-24 09:32:26 +01:00
2024-11-06 19:06:40 +09:00
2025-03-10 03:23:47 +09:00
2024-12-25 17:00:31 +01:00
2024-11-18 15:18:26 +09:00