From 25f63d467187693c0a821bb2b463f8faf627bcfe Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Tue, 31 Aug 2010 12:25:22 -0400 Subject: [PATCH] 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. --- man/systemctl.xml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/man/systemctl.xml b/man/systemctl.xml index 768f3add..63598723 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -342,9 +342,18 @@ Start the unit specified on the command line and its - dependencies and stop all others. Note - that this works only on units where - is + dependencies and stop all others. + + This is similar to changing the + runlevel in a traditional init system. The + isolate command will + immediately stop processes that are not + enabled in the new unit, possibly including + the graphical environment or terminal you + are currently using. + + Note that this works only on units + where is enabled. See systemd.unit5 for details. -- 2.39.5