chiark
/
gitweb
/
~ianmdlvl
/
elogind.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
bfa501e
)
man: clarify the effect of replace-irreversibly on future conflicting jobs
author
David Strauss
<david@davidstrauss.net>
Mon, 9 Jun 2014 22:32:03 +0000
(15:32 -0700)
committer
David Strauss
<david@davidstrauss.net>
Mon, 9 Jun 2014 22:32:03 +0000
(15:32 -0700)
man/systemctl.xml
patch
|
blob
|
history
diff --git
a/man/systemctl.xml
b/man/systemctl.xml
index b287d7ac84c8dfd7cfa5e5825f3dd539acefd071..e971b3422a4e9bf0e6ad8481819a62c1a214c568 100644
(file)
--- a/
man/systemctl.xml
+++ b/
man/systemctl.xml
@@
-230,8
+230,10
@@
along with systemd; If not, see <http://www.gnu.org/licenses/>.
<para>If <literal>replace-irreversibly</literal> is specified,
operate like <literal>replace</literal>, but also mark the new
jobs as irreversible. This prevents future conflicting
<para>If <literal>replace-irreversibly</literal> is specified,
operate like <literal>replace</literal>, but also mark the new
jobs as irreversible. This prevents future conflicting
- transactions from replacing these jobs. The jobs can still be
- cancelled using the <command>cancel</command> command.</para>
+ transactions from replacing these jobs (or even being enqueued
+ while the irreversible jobs are still pending). Irreversible
+ jobs can still be cancelled using the <command>cancel</command>
+ command.</para>
<para><literal>isolate</literal> is only valid for start
operations and causes all other units to be stopped when the
<para><literal>isolate</literal> is only valid for start
operations and causes all other units to be stopped when the