test/test-execute/exec-condition-skip.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=Test for exec condition that triggers skipping

[Service]
Type=oneshot

# exit codes [1, 254] will result in skipping the rest of execution
ExecCondition=/bin/sh -c 'exit 0'
ExecCondition=/bin/sh -c 'exit 254'

# This would normally fail the unit but will not get run due to the skip above
ExecCondition=/bin/sh -c 'exit 255'

# This should not get run
ExecStart=sh -c '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 18:07:22 +02:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
core: ExecCondition= for services Closes #10596 2019-06-28 17:02:30 -07:00			`[Unit]`
			`Description=Test for exec condition that triggers skipping`

			`[Service]`
			`Type=oneshot`

			`# exit codes [1, 254] will result in skipping the rest of execution`
			`ExecCondition=/bin/sh -c 'exit 0'`
			`ExecCondition=/bin/sh -c 'exit 254'`

			`# This would normally fail the unit but will not get run due to the skip above`
			`ExecCondition=/bin/sh -c 'exit 255'`

			`# This should not get run`
tests: use relative paths in ExecStart= and friends We want to retain some of the full paths in order to test more code paths. But the default should be to use the command name only. This makes the tests less visually cluttered. 2024-01-04 15:24:52 +01:00			`ExecStart=sh -c 'true'`