shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-31 14:50:15 +03:00
Code

man: extend documentation on systemctl isolate

Browse Source 
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.
This commit is contained in:
Matthew Miller 2010-08-31 12:25:22 -04:00 committed by Lennart Poettering
parent f73d93a4d9
commit 25f63d4671
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
man/systemctl.xml
View File

@ -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>