Systemd/test
Martin Pitt 77354c7e6f sysv-generator: Replace Provides: symlinks with real units
Since commit b7e7184 the SysV generator creates symlinks for all "Provides:" in
the LSB header. However, this is too greedy; there are cases where the
creation of a unit .service file fails because of an already existing
symlink with the same name:

 - Backup files such as /etc/init.d/foo.bak still have "Provides: foo", and
   thus get a foo.service -> foo.bak.service link. foo.bak would not be enabled
   in rcN.d/, but we (deliberately) create units for all executables in init.d/
   so that a manual "systemctl start" works. If foo.bak is processed before,
   the symlink already exists.

 - init.d/bar has "Provides: foo", while there also is a real init.d/foo. The
   former would create a link foo.service -> bar.service, while the latter
   would fail to create the real foo.service.

If we encounter an existing symlink, just remove it before writing a real unit.

Note that two init.d scripts "foo" and "bar" which both provide the same name
"common" already work. The first processed init script wins and creates the
"common.service" symlink, and the second just fails to create the symlink
again. Thus create an additional test case for this to ensure that it keeps
working sensibly.

https://bugs.debian.org/775404
2015-01-21 17:01:00 +01:00
..
bus-policy bus-policy: also add in other bus policy tests from dbus1 2014-11-26 20:58:34 +01:00
loopy.service.d core: do not add dependencies to self 2014-08-07 20:42:58 -04:00
TEST-01-BASIC
TEST-02-CRYPTSETUP
TEST-03-JOBS test: add test for crash when adding a JOB_NOP 2014-11-26 16:33:40 +01:00
.gitignore
a.service
b.service
basic.target
c.service
d.service
daughter.service
e.service
end.service
exec-environment-empty.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-environment-multiple.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-environment.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-group.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-ignoresigpipe-no.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-ignoresigpipe-yes.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-personality-x86-64.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-personality-x86.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-privatedevices-no.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-privatedevices-yes.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-privatetmp-no.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-privatetmp-yes.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-systemcallerrornumber.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-systemcallfilter-failing.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-systemcallfilter-failing2.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-systemcallfilter-not-failing.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-systemcallfilter-not-failing2.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-umask-0177.service test-execute: add tests for UMask directive 2014-12-11 18:32:57 +01:00
exec-umask-default.service test-execute: add tests for UMask directive 2014-12-11 18:32:57 +01:00
exec-user.service tests: add test-execute 2014-11-13 10:39:51 +01:00
exec-workingdirectory.service tests: add test-execute 2014-11-13 10:39:51 +01:00
f.service
g.service
grandchild.service
h.service
hello-after-sleep.target
hello.service
loopy.service core: do not add dependencies to self 2014-08-07 20:42:58 -04:00
loopy2.service core: do not add dependencies to self 2014-08-07 20:42:58 -04:00
loopy3.service core: warn when merged units have conflicting dependencies 2014-08-07 20:46:49 -04:00
loopy4.service core: warn when merged units have conflicting dependencies 2014-08-07 20:46:49 -04:00
Makefile
parent-deep.slice
parent.slice
path-changed.path tests: add test-path 2014-11-08 22:45:56 +01:00
path-changed.service tests: add test-path 2014-11-08 22:45:56 +01:00
path-directorynotempty.path tests: add test-path 2014-11-08 22:45:56 +01:00
path-directorynotempty.service tests: add test-path 2014-11-08 22:45:56 +01:00
path-exists.path tests: add test-path 2014-11-08 22:45:56 +01:00
path-exists.service tests: add test-path 2014-11-08 22:45:56 +01:00
path-existsglob.path tests: add test-path 2014-11-08 22:45:56 +01:00
path-existsglob.service tests: add test-path 2014-11-08 22:45:56 +01:00
path-makedirectory.path tests: add test-path 2014-11-08 22:45:56 +01:00
path-makedirectory.service tests: add test-path 2014-11-08 22:45:56 +01:00
path-modified.path tests: add test-path 2014-11-08 22:45:56 +01:00
path-modified.service tests: add test-path 2014-11-08 22:45:56 +01:00
path-mycustomunit.service tests: add test-path 2014-11-08 22:45:56 +01:00
path-service.service tests: add test-path 2014-11-08 22:45:56 +01:00
path-unit.path tests: add test-path 2014-11-08 22:45:56 +01:00
paths.target
README.testsuite
rule-syntax-check.py test: simplify rules-test.sh wrapper 2015-01-20 20:52:25 +01:00
sched_idle_bad.service
sched_idle_ok.service
sched_rr_bad.service
sched_rr_change.service
sched_rr_ok.service
shutdown.target
sleep.service
sockets.target
son.service
sys.tar.xz
sysinit.target
sysv-generator-test.py sysv-generator: Replace Provides: symlinks with real units 2015-01-21 17:01:00 +01:00
test-functions
testsuite.target
timers.target
udev-test.pl tests: udev - assume /etc/machine-id rather than /etc/hosts 2014-12-11 14:17:35 +01:00
unstoppable.service

The extended testsuite only works with uid=0. It contains of several
subdirectories named "test/TEST-??-*", which are run one by one.

To run the extended testsuite do the following:

$ make all
$ cd test
$ sudo make clean check
...
make[1]: Entering directory `/mnt/data/harald/git/systemd/test/TEST-01-BASIC'
Making all in .
Making all in po
Making all in docs/libudev
Making all in docs/gudev
TEST: Basic systemd setup [OK]
make[1]: Leaving directory `/mnt/data/harald/git/systemd/test/TEST-01-BASIC'
...

If one of the tests fails, then $subdir/test.log contains the log file of
the test.

To debug a special testcase of the testsuite do:

$ make all
$ cd test/TEST-01-BASIC
$ sudo make clean setup run

QEMU
====

If you want to log in the testsuite virtual machine, you can specify
additional kernel command line parameter with $KERNEL_APPEND.

$ sudo make KERNEL_APPEND="systemd.unit=multi-user.target" clean setup run

you can even skip the "clean" and "setup" if you want to run the machine again.

$ sudo make KERNEL_APPEND="systemd.unit=multi-user.target" run

You can specify a different kernel and initramfs with $KERNEL_BIN and $INITRD.
(Fedora's default kernel path and initramfs are used by default)

$ sudo make KERNEL_BIN=/boot/vmlinuz-foo INITRD=/boot/initramfs-bar clean check

A script will try to find your QEMU binary. If you want to specify a different
one you can use $QEMU_BIN.

$ sudo make QEMU_BIN=/path/to/qemu/qemu-kvm clean check