| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
service, rely on manual symlinks to allow disabling of dbus services
|
|
|
|
before creating $foo wants links
|
|
cgroup to die, too
|
|
|
|
|
|
|
|
if it left our service cgroup
Related to:
http://bugzilla.redhat.com/show_bug.cgi?id=626477
|
|
|
|
|
|
|
|
|
|
|
|
decode exit codes in systemctl
|
|
output on the TTY in all cases
|
|
|
|
|
|
|
|
lines for oneshot services
In contrast to the other service types oneshot services are usually not
long lasting and there's not necessarily a single clean main process for
them. This change allows multiple ExecStart= lines for this type of
services so that the admin/developer doesn't have to arbitrarily pick on
of various sequential commands as the "main one".
|
|
|
|
|
|
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.
|
|
|
|
Previously we checked the SysV priority value to figure out if a SysV
unit was enabled or not, since th value was mostly read from the S
startup links. Since we read this value from the LSB headers as a
fallback we hence ended up considering a lot more services enabled than
were actually enabled.
This patch adds an explicit boolean which encodes whether a sysv service
is enabled or not via S links.
https://bugzilla.redhat.com/show_bug.cgi?id=615293
|
|
|
|
|
|
normal runlevels
|
|
|
|
network.target or other LSB-style Provides: targets
|
|
|
|
|
|
instantiation to start without a socket
|
|
stop-post command
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for acquiring it again in the reload/stop step
|
|
|
|
|
|
|
|
logging is disabled, for diagnostic purposes
|
|
|
|
size
|
|
|
