Our coding style says static variables suck except for very special cases, i.e. things like the log level or very per-process stuff, such as parsed version of cmdline args and such. sysusers departed from that as one of the very few exceptions in our codebases: it keeps its operational state in global variables. Address that. Introduce a Context object that carries the fields that so far have been global, and pass it around as needed. This has the nice effect that state and configuration is clearly separated in code, and we can very clearly see which functions mangle state and which ones do not. No actual codeflow changes, just refactoring.
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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
