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.
|
|
|
|
others should be added via .wants/ links
|
|
|
|
|
|
|
|
|
|
root dir
|
|
|
|
|
|
|
|
|
|
This should fix accounting for pam_limits and suchlike.
https://bugzilla.redhat.com/show_bug.cgi?id=636036
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=636752
|
|
The current behavior of the /proc/self/mountinfo parser
is to stop the parser on parse failures
I'm only changing this behavior to try the next line and adding
a warning if occurs a fail.
|
|
|
|
|
|
|
|
|
|
|
|
if it left our service cgroup
Related to:
http://bugzilla.redhat.com/show_bug.cgi?id=626477
|
|
|
|
|
|
|
|
|
|
there
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for acquiring it again in the reload/stop step
|
|
|
|
|
|
|
|
|