systemd/test/test-execute/exec-privatenetwork-yes-privatemounts-yes.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=Test for PrivateNetwork= with mount namespacing

[Service]
ExecStart=sh -x -c '! ip link show dummy-test-exec'
ExecStart=sh -x -c 'test ! -e /proc/sys/net/ipv4/conf/dummy-test-exec'
# With mount namespacing, we cannot access the dummy-test-exec interface through sysfs.
ExecStart=sh -x -c 'test ! -e /sys/class/net/dummy-test-exec'
Type=oneshot
PrivateNetwork=yes
# PrivateNetwork=yes implies PrivateMounts=yes
test-execute: add test for PrivateNetwork= with/without mount namespacing 2023-02-17 05:26:29 +00:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
			`[Unit]`
			`Description=Test for PrivateNetwork= with mount namespacing`

			`[Service]`
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 14:24:52 +00:00			`ExecStart=sh -x -c '! ip link show dummy-test-exec'`
			`ExecStart=sh -x -c 'test ! -e /proc/sys/net/ipv4/conf/dummy-test-exec'`
test-execute: add test for PrivateNetwork= with/without mount namespacing 2023-02-17 05:26:29 +00:00			`# With mount namespacing, we cannot access the dummy-test-exec interface through sysfs.`
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 14:24:52 +00:00			`ExecStart=sh -x -c 'test ! -e /sys/class/net/dummy-test-exec'`
test-execute: add test for PrivateNetwork= with/without mount namespacing 2023-02-17 05:26:29 +00:00			`Type=oneshot`
			`PrivateNetwork=yes`
			`# PrivateNetwork=yes implies PrivateMounts=yes`