systemd/test/testsuite-07.units/issue2467.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Requires=issue2467.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
tests: add spdx license header to test unit/link/network/conf files Those are all consumed by our parser, so they all support comments. I was considering whether they should have a license header at all, but in the end I decided to add it because those files are often created by copying parts of real unit files. And if the real ones have a license, then those might as well. It's easier to add it than to make an exception. 2021-10-17 19:07:22 +03:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
test: move TEST-10-ISSUE-2467 setup to static files 2019-12-09 22:42:48 +03:00			`[Unit]`
test: merge TEST-10-ISSUE-2467 with TEST-07-PID1 2023-05-10 14:41:03 +03:00			`Requires=issue2467.socket`
test: move TEST-10-ISSUE-2467 setup to static files 2019-12-09 22:42:48 +03:00			`ConditionPathExistsGlob=/tmp/nonexistent`
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-24 18:46:47 +03:00			`# Make sure we hit the socket trigger limit in the test and not the service start limit.`
			`StartLimitInterval=1000`
			`StartLimitBurst=1000`
test: move TEST-10-ISSUE-2467 setup to static files 2019-12-09 22:42:48 +03:00
			`[Service]`
			`ExecStart=true`