| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
In order to simplify writing of unit files introduce default
dependencies that are added to all units unless explictly disabled in a
unit. This option can be switched off for select units that are involved
in early boot-up ot late system shutdown,
This should simplify service files for most normal daemons, but breaks
existing service files for software involved in early boot (notably
udev), which need to be updated for a DefaultDependencies=no setting)
|
|
one step
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
