mirror of
https://github.com/systemd/systemd.git
synced 2024-11-07 01:27:11 +03:00
The systemd System and Service Manager
913c19161a
start_unit() is a little tangled. There's an easy part we can untangle, then readers can concentrate on the more necessary complexity. * Derive (method, action, mode) more clearly, as disjoint cases based on the command. Don't rely on action_table[_ACTION_INVALID].target being implicitly initialized to NULL. verb_to_method() is now only used on one case, but not because I strongly object to the implicit "StartUnit" cases. It's more a syntax problem. I think the old code takes me longer to understand, because the call comes just above a similar-looking call to verb_to_action(), but the results of the two functions are used in different ways. It also helps that the new code ends up having a more regular form, for the 4 different cases. These changes cost 6 extra lines. * Add an assertion to confirm that we do not pass mode=NULL. |
||
---|---|---|
.github | ||
.mkosi | ||
catalog | ||
coccinelle | ||
docs | ||
factory/etc | ||
hwdb | ||
man | ||
modprobe.d | ||
network | ||
po | ||
rules | ||
shell-completion | ||
src | ||
sysctl.d | ||
system-preset | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.travis.yml | ||
.vimrc | ||
.ycm_extra_conf.py | ||
CODING_STYLE | ||
configure | ||
DISTRO_PORTING | ||
ENVIRONMENT.md | ||
HACKING | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
Makefile | ||
meson_options.txt | ||
meson.build | ||
mkosi.build | ||
mkosi.default | ||
NEWS | ||
README | ||
README.md | ||
TODO |
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements are provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the HACKING file for information 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.