summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorMatthew Miller <mattdm@mattdm.org>2010-08-31 12:25:22 -0400
committerLennart Poettering <lennart@poettering.net>2010-09-03 04:48:00 +0200
commit25f63d467187693c0a821bb2b463f8faf627bcfe (patch)
treefe7ffbad73b5fb35f62d194dee6715ca3b6e50cc /man
parentf73d93a4d9403d44bf3661bf383ac1385e5b5eb6 (diff)
man: extend documentation on systemctl isolate
Lennart has convinced me that it's more helpful to participate than to sit on the sidelines and complain. So, hello everyone. I'm starting by giving up the battle to change the systemctl "isolate" command to "switch-to". Can't win them all. :) I've got a suggested patch to expand the documentation a bit, hopefully making it more clear to new systemd users. Is there an easy way to list all units where AllowIsolate is enabled? That should be included alongside this, I think.
Diffstat (limited to 'man')
-rw-r--r--man/systemctl.xml15
1 files changed, 12 insertions, 3 deletions
diff --git a/man/systemctl.xml b/man/systemctl.xml
index 768f3add59..63598723bb 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -342,9 +342,18 @@
<listitem><para>Start the unit
specified on the command line and its
- dependencies and stop all others. Note
- that this works only on units where
- <option>AllowIsolate=</option> is
+ dependencies and stop all others.</para>
+
+ <para>This is similar to changing the
+ runlevel in a traditional init system. The
+ <command>isolate</command> command will
+ immediately stop processes that are not
+ enabled in the new unit, possibly including
+ the graphical environment or terminal you
+ are currently using.</para>
+
+ <para>Note that this works only on units
+ where <option>AllowIsolate=</option> is
enabled. See
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details.</para></listitem>