From: David Strauss <david@davidstrauss.net>
Date: Mon, 9 Jun 2014 22:32:03 +0000 (-0700)
Subject: man: clarify the effect of replace-irreversibly on future conflicting jobs
X-Git-Tag: v214~39
X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;ds=sidebyside;h=9a92e77e4325b995288ef7cac144ecbf969886df;hp=bfa501e150e05d6232d4d1fd7f881807a9924a41;p=elogind.git

man: clarify the effect of replace-irreversibly on future conflicting jobs
---

diff --git a/man/systemctl.xml b/man/systemctl.xml
index b287d7ac8..e971b3422 100644
--- 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
-        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