Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
weaker counterpart of Conflicts=, similar to Wants= vs. Requires=
|
|
The property StopRetroactively= needs to be per-dependency, not
per-unit, in order to properly express dependencies between .mount units
and its .device and fsck .service units. If the .device unit is
unplugged the mount should go away, but if the fsck process terminates
the .mount should stay.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
aliased swap disks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=627785
|
|
|
|
|
|
We should not avoid stopping services when using isolate, since that
kinda defeats the point of it.
http://bugzilla.redhat.com/show_bug.cgi?id=627014
|
|
|
|
It is essential that the gettys are proper dependencies from
getty.target so that they aren't killed and immediately restarted on
runlevel changes. Hence rework the logic to implicitly add console
gettys to getty.target as dependencies.
This also adds an automatic hvc console for virtualizers.
https://bugzilla.redhat.com/show_bug.cgi?id=501720
|
|
|
|
decode exit codes in systemctl
|
|
|
|
|
|
|
|
essential
|
|
|
|
|
|
|
|
|
|
|
|
and into a helper binary
|
|
remove the one that is "conflicted"
This gives the writer of units control which unit is kept and which is
stopped when two units conflict.
|
|
|
|
|
|
|
|
|
|
|