Lennart Poettering
a932d2f23e
Previously, one of the io.systemd.Machine.Open() tests would invoke a command line via machined, and then check if it ran properly. This was implemented in a racy fashion: the client side would immediately close the pty fd allocated for the operation, thus triggering an immediate SIGHUP on the other side. Now, depending whether this client was quicker in closing or the server was quicker in executing the command line this was a race. Fix this comprehensively: let's first wait for the varlink operation to complete via the new "systemd-notify --fork" logic (because varlinkctl sends out READY=1 once handing off to --exec). Secondly let's use varlinkctl's --exec logic to invoke a process which keeps open the open pty until we kill it (we just use sleep for that). (Also add some more tests for the varlinkctl --exec stuff)
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