systemd/test/test-execute/exec-specifier@.service

[Unit]
Description=Test for specifiers (template unit)

[Service]
Type=oneshot
ExecStart=test %n = exec-specifier@foo-bar.service
ExecStart=test %N = exec-specifier@foo-bar
ExecStart=test %p = exec-specifier
ExecStart=test %P = exec/specifier
ExecStart=test %i = foo-bar
ExecStart=test %I = foo/bar
ExecStart=test %j = specifier
ExecStart=test %J = specifier
ExecStart=test %f = /foo/bar
ExecStart=test %t = /run
ExecStart=test %S = /var/lib
ExecStart=test %C = /var/cache
ExecStart=test %L = /var/log
ExecStart=sh -c 'test %u = $$(id -un 0)'
ExecStart=test %U = 0
ExecStart=sh -c 'test %h = $$(getent passwd 0 | cut -d: -f 6)'
ExecStart=sh -c 'test %s = /bin/sh'
ExecStart=sh -c 'test %m = $$(cat /etc/machine-id)'
ExecStart=sh -c 'test %b = $$(cat /proc/sys/kernel/random/boot_id | sed -e 's/-//g')'
ExecStart=sh -c 'test %H = $$(hostname)'
ExecStart=sh -c 'test %v = $$(uname -r)'
test-execute: cleanup This makes rename the test units by a consistent naming scheme, add several logs, and sort internal functions. No functional change. 2017-12-05 18:36:55 +03:00			`[Unit]`
			`Description=Test for specifiers (template unit)`

test-execute: test more % specifiers (#7450) 2017-11-24 12:17:28 +03:00			`[Service]`
			`Type=oneshot`
test: drop the use of /bin/sh in various test services This is not meant to be comprehensive, just the few cases where the /bin/sh -c wrapper is obviously superfluous. 2018-03-25 22:10:50 +03:00			`ExecStart=test %n = exec-specifier@foo-bar.service`
			`ExecStart=test %N = exec-specifier@foo-bar`
			`ExecStart=test %p = exec-specifier`
			`ExecStart=test %P = exec/specifier`
			`ExecStart=test %i = foo-bar`
			`ExecStart=test %I = foo/bar`
test: add tests for %j and %J specifier in test-execute (#8838) Follow-up for 250e9fadbcc0ca90e697d7efb40855b054ed3b8f. 2018-04-27 14:07:23 +03:00			`ExecStart=test %j = specifier`
			`ExecStart=test %J = specifier`
test: drop the use of /bin/sh in various test services This is not meant to be comprehensive, just the few cases where the /bin/sh -c wrapper is obviously superfluous. 2018-03-25 22:10:50 +03:00			`ExecStart=test %f = /foo/bar`
			`ExecStart=test %t = /run`
			`ExecStart=test %S = /var/lib`
			`ExecStart=test %C = /var/cache`
			`ExecStart=test %L = /var/log`
			`ExecStart=sh -c 'test %u = $$(id -un 0)'`
			`ExecStart=test %U = 0`
			`ExecStart=sh -c 'test %h = $$(getent passwd 0 \| cut -d: -f 6)'`
tests: compare with correct shell We synthesize the passwd record for UID 0, hence we need to compare with our synthesized data and not with the data stored in /etc/passwd 2018-04-19 11:35:36 +03:00			`ExecStart=sh -c 'test %s = /bin/sh'`
test: drop the use of /bin/sh in various test services This is not meant to be comprehensive, just the few cases where the /bin/sh -c wrapper is obviously superfluous. 2018-03-25 22:10:50 +03:00			`ExecStart=sh -c 'test %m = $$(cat /etc/machine-id)'`
			`ExecStart=sh -c 'test %b = $$(cat /proc/sys/kernel/random/boot_id \| sed -e 's/-//g')'`
			`ExecStart=sh -c 'test %H = $$(hostname)'`
			`ExecStart=sh -c 'test %v = $$(uname -r)'`