mirror of
https://github.com/systemd/systemd.git
synced 2024-11-01 09:21:26 +03:00
9727f2427f
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.
10 lines
231 B
Desktop File
10 lines
231 B
Desktop File
[Unit]
|
|
Requires=test10.socket
|
|
ConditionPathExistsGlob=/tmp/nonexistent
|
|
# Make sure we hit the socket trigger limit in the test and not the service start limit.
|
|
StartLimitInterval=1000
|
|
StartLimitBurst=1000
|
|
|
|
[Service]
|
|
ExecStart=true
|