mirror of
https://github.com/systemd/systemd-stable.git
synced 2025-01-08 21:17:47 +03:00
Backports of patch from systemd git to stable distributions
3d083b2245
Previously, we'd explicitly use "GetUnit()" on the server side to convert a unit name into a bus path, as that function will return an error if the unit is not currently loaded. If we'd convert the path on the client side, and access the unit this way directly the unit would be loaded automatically in the background. The old logic was done in order to minimize the effect of "is-active" on the system, i.e. that a monoitoring command does not itself alter the state of the system. however, this is problematic as this can lead to confusing results if the queried unit name is an alias that currently is not loaded: we'd claim the unit wasn't active even though this isn't strictly true: the unit the name is an alias for might be. Hence, let's simplify the code, and accept that we might end up loading a unit briefly here, and let's make "systemctl is-active" skip the GetUnit() thing and calculate the unit path right away. Fixes: #7875 |
||
---|---|---|
.github | ||
.mkosi | ||
catalog | ||
coccinelle | ||
docs | ||
factory/etc | ||
hwdb | ||
man | ||
modprobe.d | ||
network | ||
po | ||
presets | ||
rules | ||
scripts | ||
shell-completion | ||
src | ||
sysctl.d | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
travis-ci | ||
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 | ||
TRANSIENT-SETTINGS.md | ||
UIDS-GIDS.md |
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.