Daan De Meyer 9727f2427f core: Check unit start rate limiting earlier ... 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.		2021-08-25 13:26:14 +01:00
..
test10.service	core: Check unit start rate limiting earlier	2021-08-25 13:26:14 +01:00
test10.socket