Christian Brauner
7ed34c0498
Replace the random hex suffix in the runtime directory with the machine name, changing the layout from /run/systemd/vmspawn.<random> to /run/systemd/vmspawn/<machine-name>/. This makes runtime directories machine-discoverable from the filesystem and groups all vmspawn instances under a shared parent directory, similar to how nspawn uses /run/systemd/nspawn/. Use runtime_directory_generic() instead of runtime_directory() since vmspawn is not a service with RuntimeDirectory= set and the $RUNTIME_DIRECTORY check in the latter never succeeds. The directory is always created by vmspawn itself and cleaned up via rm_rf_physical_and_freep on exit. The parent vmspawn/ directory is intentionally left behind as a shared namespace.
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