mirror of
https://github.com/systemd/systemd
synced 2024-09-06 08:46:19 +00:00
![]() Fixes #17433. Currently, if any of the validations we do before we check start rate limiting fail, we can still enter a busy loop as no rate limiting gets applied. A common occurence of this scenario is path units triggering a service that fails a condition check. To fix the issue, we simply move up start rate limiting checks to be the first thing we do when starting a unit. To achieve this, we add a new method to the unit vtable and implement it for the relevant unit types so that we can do the start rate limit checks earlier on. |
||
---|---|---|
.. | ||
test63.path | ||
test63.service |