| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
single user mode
|
|
|
|
|
|
|
|
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=623802
|
|
|
|
|
|
processes/shut down
|
|
shutdown/boot, but don't enable it by default
|
|
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".
|
|
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=623561
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=623430
|
|
|
|
RefuseManualStop=
Some unit shall never be start on user request (e.g. shutdown.target)
others never be stopped on user request (e.g. auditd.servce), hence
offer options for both.
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=619922
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
seperate arguments
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
rescue/emergency modes
|
|
|
|
|
|
|
