Luca Boccassi
4394046ee6
If a unit has active jobs, when it gets serialized there are job subsections, each with their own empty line marker. The skipping function ignores this and skips until the marker, but then leaves the job in place, breaking deserialization. Consume jobs subsections too. This shows up now that there's TEST-07-PID1.alias-corruption, which occasionally fails when the aliased unit happens to still have a job when the reexec happens. [ 967.551630] TEST-07-PID1.sh[179]: + echo 'Testing with: systemctl daemon-reexec' [ 967.551630] TEST-07-PID1.sh[179]: Testing with: systemctl daemon-reexec [ 968.405274] TEST-07-PID1.sh[179]: + echo '--- Attempt 1/3 ---' [ 968.405274] TEST-07-PID1.sh[179]: --- Attempt 1/3 --- [ 968.698641] TEST-07-PID1.sh[179]: + echo 'Running daemon-reexec...' [ 968.698641] TEST-07-PID1.sh[179]: Running daemon-reexec... [ 969.130261] TEST-07-PID1.sh[179]: + echo 'legit.service PID remains 1282. Attempt 1 passed.' [ 969.130261] TEST-07-PID1.sh[179]: legit.service PID remains 1282. Attempt 1 passed. [ 970.870456] TEST-07-PID1.sh[179]: + echo '--- Attempt 2/3 ---' [ 970.870456] TEST-07-PID1.sh[179]: --- Attempt 2/3 --- [ 971.267205] TEST-07-PID1.sh[179]: + echo 'Running daemon-reexec...' [ 971.267205] TEST-07-PID1.sh[179]: Running daemon-reexec... [ 971.715743] TEST-07-PID1.sh[179]: + echo 'legit.service PID changed from 1282 to 1643!' [ 971.715743] TEST-07-PID1.sh[179]: legit.service PID changed from 1282 to 1643! Follow-up fora77c7a8224Follow-up for0742986650
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.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release