test/test-execute/exec-basic.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=Test for basic execution
ConditionKernelVersion=">=3.0"
ConditionKernelVersion=">=2.0" "<=60" "!=1.4"
ConditionKernelVersion=" >= 2.0" " <= 60 " "!= 1.4"
ConditionKernelVersion=" >= 2.0" " * " "*.*"

ConditionVersion=kernel ">=3.0"
ConditionVersion=kernel ">=2.0" "<=60" "!=1.4"
ConditionVersion=kernel " >= 2.0" " <= 60 " "!= 1.4"
ConditionVersion=kernel " >= 2.0" " * " "*.*"

ConditionVersion=">=3.0"
ConditionVersion=">=2.0" "<=60" "!=1.4"
ConditionVersion=" >= 2.0" " <= 60 " "!= 1.4"
ConditionVersion=" >= 2.0" " * " "*.*"

ConditionVersion=systemd ">=30"
ConditionVersion=systemd ">=20" "<=9000" "!=14"
ConditionVersion=systemd " >= 20" " <= 9000 " "!= 14"
ConditionVersion=systemd " >= 20" " * "

ConditionVersion=glibc ">=2"
ConditionVersion=glibc ">=2" "<=9000" "!=1"
ConditionVersion=glibc " >= 2" " <= 9000 " "!= 1"
ConditionVersion=glibc " >= 2" " * "

[Service]
ExecStart=touch /tmp/a ; /bin/sh -c 'touch /tmp/b' ; touch /tmp/c
ExecStart=test -f /tmp/a
ExecStart=!test -f /tmp/b
ExecStart=!!test -f /tmp/c
ExecStartPost=rm /tmp/a /tmp/b /tmp/c

PrivateTmp=true
Type=oneshot
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`
systemd: do not require absolute paths in ExecStart Absolute paths make everything simple and quick, but sometimes this requirement can be annoying. A good example is calling 'test', which will be located in /usr/bin/ or /bin depending on the distro. The need the provide the full path makes it harder a portable unit file in such cases. This patch uses a fixed search path (DEFAULT_PATH which was already used as the default value of $PATH), and if a non-absolute file name is found, it is immediately resolved to a full path using this search path when the unit is loaded. After that, everything behaves as if an absolute path was specified. In particular, the executable must exist when the unit is loaded. 2018-03-25 20:50:15 +02:00			`[Unit]`
			`Description=Test for basic execution`
test-execute: add test for ConditionKernelVersion= with quotation 2019-06-27 23:11:34 +09:00			`ConditionKernelVersion=">=3.0"`
			`ConditionKernelVersion=">=2.0" "<=60" "!=1.4"`
Treat kernel version condition as a list of quoted checks Before only one comparison was allowed. Let's make this more flexible: ConditionKernelVersion = ">=4.0" "<=4.5" Fixes #12881. This also fixes expressions like "ConditionKernelVersion=>" which would evaluate as true. 2019-06-28 10:58:06 +02:00			`ConditionKernelVersion=" >= 2.0" " <= 60 " "!= 1.4"`
			`ConditionKernelVersion=" >= 2.0" " * " "."`
systemd: do not require absolute paths in ExecStart Absolute paths make everything simple and quick, but sometimes this requirement can be annoying. A good example is calling 'test', which will be located in /usr/bin/ or /bin depending on the distro. The need the provide the full path makes it harder a portable unit file in such cases. This patch uses a fixed search path (DEFAULT_PATH which was already used as the default value of $PATH), and if a non-absolute file name is found, it is immediately resolved to a full path using this search path when the unit is loaded. After that, everything behaves as if an absolute path was specified. In particular, the executable must exist when the unit is loaded. 2018-03-25 20:50:15 +02:00
condition: introduce ConditionVersion=/AssertVersion= Add a new condition wich checks against systemd version. Change condition_test_kernel_version() into a generic condition_test_version() so most of the code can be reused. $ systemctl --version systemd 258 (258~devel-g53ca5f6) $ systemd-analyze condition 'ConditionVersion=systemd>255' test.service: ConditionVersion=>255 succeeded. $ systemd-analyze condition 'ConditionVersion=systemd>260' test.service: ConditionVersion=>260 failed. $ systemd-analyze condition 'ConditionVersion=systemd>=258' test.service: ConditionVersion=>=258 succeeded. $ systemd-analyze condition 'ConditionVersion=systemd>=257.1' test.service: ConditionVersion=>=257.1 succeeded. $ uname -r 6.12.13-200.fc41.aarch64 $ systemd-analyze condition 'ConditionVersion=kernel > 4.4' test.service: ConditionVersion=kernel > 4.4 succeeded. $ systemd-analyze condition 'ConditionVersion=kernel > 6.20' test.service: ConditionVersion=kernel > 6.20 failed. $ systemd-analyze condition 'ConditionVersion=kernel < 9.0' test.service: ConditionVersion=kernel < 9.0 succeeded. 2025-02-20 13:07:24 +01:00			`ConditionVersion=kernel ">=3.0"`
			`ConditionVersion=kernel ">=2.0" "<=60" "!=1.4"`
			`ConditionVersion=kernel " >= 2.0" " <= 60 " "!= 1.4"`
			`ConditionVersion=kernel " >= 2.0" " * " "."`

			`ConditionVersion=">=3.0"`
			`ConditionVersion=">=2.0" "<=60" "!=1.4"`
			`ConditionVersion=" >= 2.0" " <= 60 " "!= 1.4"`
			`ConditionVersion=" >= 2.0" " * " "."`

			`ConditionVersion=systemd ">=30"`
			`ConditionVersion=systemd ">=20" "<=9000" "!=14"`
			`ConditionVersion=systemd " >= 20" " <= 9000 " "!= 14"`
			`ConditionVersion=systemd " >= 20" " * "`

match glibc in ConditionVersion Extend ConditionVersion= to allow matching against glibc version, as proposed in https://github.com/systemd/systemd/pull/36468#issuecomment-2674600909 2025-03-16 02:48:29 +01:00			`ConditionVersion=glibc ">=2"`
			`ConditionVersion=glibc ">=2" "<=9000" "!=1"`
			`ConditionVersion=glibc " >= 2" " <= 9000 " "!= 1"`
			`ConditionVersion=glibc " >= 2" " * "`

systemd: do not require absolute paths in ExecStart Absolute paths make everything simple and quick, but sometimes this requirement can be annoying. A good example is calling 'test', which will be located in /usr/bin/ or /bin depending on the distro. The need the provide the full path makes it harder a portable unit file in such cases. This patch uses a fixed search path (DEFAULT_PATH which was already used as the default value of $PATH), and if a non-absolute file name is found, it is immediately resolved to a full path using this search path when the unit is loaded. After that, everything behaves as if an absolute path was specified. In particular, the executable must exist when the unit is loaded. 2018-03-25 20:50:15 +02:00			`[Service]`
test: let the shell find "touch" instead of hard-coded "/bin/touch" 2018-11-19 02:51:25 +08:00			`ExecStart=touch /tmp/a ; /bin/sh -c 'touch /tmp/b' ; touch /tmp/c`
systemd: do not require absolute paths in ExecStart Absolute paths make everything simple and quick, but sometimes this requirement can be annoying. A good example is calling 'test', which will be located in /usr/bin/ or /bin depending on the distro. The need the provide the full path makes it harder a portable unit file in such cases. This patch uses a fixed search path (DEFAULT_PATH which was already used as the default value of $PATH), and if a non-absolute file name is found, it is immediately resolved to a full path using this search path when the unit is loaded. After that, everything behaves as if an absolute path was specified. In particular, the executable must exist when the unit is loaded. 2018-03-25 20:50:15 +02:00			`ExecStart=test -f /tmp/a`
			`ExecStart=!test -f /tmp/b`
			`ExecStart=!!test -f /tmp/c`
			`ExecStartPost=rm /tmp/a /tmp/b /tmp/c`

			`PrivateTmp=true`
			`Type=oneshot`