Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
increase it when reexecuting
Instead of having individual counters n_serializing and n_deserializing
have a single one n_reloading, which should be sufficient.
Set n_reloading when we are about to go down for reexecution to avoid
cgroup trimming when we free the units for reexecution.
|
|
|
|
has specified an explicit path in it
|
|
|
|
|
|
type property
|
|
http://lists.freedesktop.org/archives/systemd-devel/2011-April/001910.html
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=678555
|
|
around when isolating
|
|
|
|
|
|
|
|
OnFailureIsolate= is on
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the name of the syslog implementation is
|
|
|
|
|
|
are off for either target and unit
|
|
Just some lame spelling corrections with no functionality.
|
|
dependencies, timeout
|
|
|
|
syslog/kmsg
|
|
|
|
just the reload job
|
|
|
|
|
|
cryptsetup service
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|