systemd-stable/test/TEST-63-ISSUE-17433/test.sh

#!/usr/bin/env bash
set -e

TEST_DESCRIPTION="https://github.com/systemd/systemd/issues/17433"

# shellcheck source=test/test-functions
. "${TEST_BASE_DIR:?}/test-functions"

do_test "$@"
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			`#!/usr/bin/env bash`
			`set -e`

			`TEST_DESCRIPTION="https://github.com/systemd/systemd/issues/17433"`

			`# shellcheck source=test/test-functions`
			`. "${TEST_BASE_DIR:?}/test-functions"`

			`do_test "$@"`