Otherwise we might continue too early on slower machines: [ 53.777485] testsuite-07.sh[675]: + systemd-run --unit test-aux-scope.service -p Slice=aux.slice -p Type=exec -p TasksMax=99 -p CPUWeight=199 -p IPAccounting=yes /usr/lib/systemd/tests/unit-tests/manual/test-aux-scope [ 55.399526] testsuite-07.sh[679]: Running as unit: test-aux-scope.service; invocation ID: 375dc3e2d12f4af1bedfe80a23709e37 [ 55.512917] testsuite-07.sh[691]: ++ systemctl show --value --property MainPID test-aux-scope.service [ 56.947713] testsuite-07.sh[675]: + kill -s USR1 680 [ 56.947713] testsuite-07.sh[675]: + sleep 1 [ 58.058809] testsuite-07.sh[675]: + systemctl status test-aux-scope.service [ 58.902808] testsuite-07.sh[695]: ● test-aux-scope.service - /usr/lib/systemd/tests/unit-tests/manual/test-aux-scope [ 58.902808] testsuite-07.sh[695]: Loaded: loaded (/run/systemd/transient/test-aux-scope.service; transient) [ 58.902808] testsuite-07.sh[695]: Transient: yes [ 58.902808] testsuite-07.sh[695]: Active: active (running) since Thu 2024-02-01 04:53:57 UTC; 3s ago [ 58.902808] testsuite-07.sh[695]: Main PID: 680 (test-aux-scope) [ 58.902808] testsuite-07.sh[695]: IP: 0B in, 0B out [ 58.902808] testsuite-07.sh[695]: Tasks: 11 (limit: 99) [ 58.902808] testsuite-07.sh[695]: Memory: 3.2M (peak: 3.5M) [ 58.902808] testsuite-07.sh[695]: CPU: 235ms [ 58.902808] testsuite-07.sh[695]: CGroup: /aux.slice/test-aux-scope.service [ 58.902808] testsuite-07.sh[695]: ├─680 /usr/lib/systemd/tests/unit-tests/manual/test-aux-scope [ 58.902808] testsuite-07.sh[695]: ├─681 "(worker)" [ 58.902808] testsuite-07.sh[695]: ├─682 "(worker)" [ 58.902808] testsuite-07.sh[695]: ├─683 "(worker)" [ 58.902808] testsuite-07.sh[695]: ├─684 "(worker)" [ 58.902808] testsuite-07.sh[695]: ├─685 "(worker)" [ 58.902808] testsuite-07.sh[695]: ├─686 "(worker)" [ 58.902808] testsuite-07.sh[695]: ├─687 "(worker)" [ 58.902808] testsuite-07.sh[695]: ├─688 "(worker)" [ 58.902808] testsuite-07.sh[695]: ├─689 "(worker)" [ 58.902808] testsuite-07.sh[695]: └─690 "(worker)" [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H systemd[1]: test-aux-scope.service: Enqueued job test-aux-scope.service/start as 277 [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H systemd[1]: test-aux-scope.service: Will spawn child (service_enter_start): /usr/lib/systemd/tests/unit-tests/manual/test-aux-scope [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H systemd[1]: test-aux-scope.service: Passing 0 fds to service [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H systemd[1]: test-aux-scope.service: About to execute: /usr/lib/systemd/tests/unit-tests/manual/test-aux-scope [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H systemd[1]: test-aux-scope.service: Forked /usr/lib/systemd/tests/unit-tests/manual/test-aux-scope as 680 [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H systemd[1]: test-aux-scope.service: Changed dead -> start [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H systemd[1]: Starting test-aux-scope.service... [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H systemd-executor[680]: SELinux enabled state cached to: disabled [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H (ux-scope)[680]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy [ 58.902808] testsuite-07.sh[695]: Feb 01 04:53:57 H (ux-scope)[680]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy [ 58.979659] testsuite-07.sh[701]: ++ ps -eo pid,unit [ 59.014968] testsuite-07.sh[702]: ++ grep -c test-aux-scope.service [ 59.729453] systemd[1]: Cannot find unit for notify message of PID 691, ignoring. [ 60.321547] testsuite-07.sh[675]: + test 11 = 1 [ 60.332496] testsuite-07.sh[669]: + echo 'Subtest /usr/lib/systemd/tests/testdata/units/testsuite-07.aux-scope.sh failed'
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
