mirror of
https://github.com/systemd/systemd.git
synced 2024-11-13 23:21:08 +03:00
264581a2f1
While the LSB suggests only [A-Za-z0-9], that doesn't prevent admins from doing the wrong thing. Lets not generate invalid names in that case. |
||
|---|---|---|
| .. | ||
| bus-policy | ||
| loopy.service.d | ||
| mocks | ||
| TEST-01-BASIC | ||
| TEST-02-CRYPTSETUP | ||
| TEST-03-JOBS | ||
| .gitignore | ||
| a.service | ||
| b.service | ||
| basic.target | ||
| c.service | ||
| d.service | ||
| daughter.service | ||
| e.service | ||
| end.service.in | ||
| exec-environment-empty.service | ||
| exec-environment-multiple.service | ||
| exec-environment.service | ||
| exec-group.service | ||
| exec-ignoresigpipe-no.service | ||
| exec-ignoresigpipe-yes.service | ||
| exec-personality-x86-64.service | ||
| exec-personality-x86.service | ||
| exec-privatedevices-no.service | ||
| exec-privatedevices-yes.service | ||
| exec-privatetmp-no.service | ||
| exec-privatetmp-yes.service | ||
| exec-systemcallerrornumber.service | ||
| exec-systemcallfilter-failing2.service | ||
| exec-systemcallfilter-failing.service | ||
| exec-systemcallfilter-not-failing2.service | ||
| exec-systemcallfilter-not-failing.service | ||
| exec-umask-0177.service | ||
| exec-umask-default.service | ||
| exec-user.service | ||
| exec-workingdirectory.service | ||
| f.service | ||
| g.service | ||
| grandchild.service | ||
| h.service | ||
| hello-after-sleep.target | ||
| hello.service | ||
| loopy2.service | ||
| loopy3.service | ||
| loopy4.service | ||
| loopy.service | ||
| Makefile | ||
| parent-deep.slice | ||
| parent.slice | ||
| path-changed.path | ||
| path-changed.service | ||
| path-directorynotempty.path | ||
| path-directorynotempty.service | ||
| path-exists.path | ||
| path-exists.service | ||
| path-existsglob.path | ||
| path-existsglob.service | ||
| path-makedirectory.path | ||
| path-makedirectory.service | ||
| path-modified.path | ||
| path-modified.service | ||
| path-mycustomunit.service | ||
| path-service.service | ||
| path-unit.path | ||
| paths.target | ||
| README.testsuite | ||
| rule-syntax-check.py | ||
| 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 | ||
| splash.bmp | ||
| sys.tar.xz | ||
| sysinit.target | ||
| sysv-generator-test.py | ||
| test-efi-create-disk.sh | ||
| test-functions | ||
| testsuite.target | ||
| timers.target | ||
| udev-test.pl | ||
| 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 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