From: Lennart Poettering Date: Tue, 17 Jul 2018 11:05:39 +0000 (+0200) Subject: man: fix --ignore-inhibitors docs X-Git-Tag: v240~966 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=81d39f0d2cd63e35389df7b9ebefc3049d1a2305;p=thirdparty%2Fsystemd.git man: fix --ignore-inhibitors docs Reported here: https://lists.freedesktop.org/archives/systemd-devel/2018-June/040939.html Also see: https://lists.freedesktop.org/archives/systemd-devel/2018-July/041036.html --- diff --git a/man/systemctl.xml b/man/systemctl.xml index a70bdb40d7f..d4a915e4565 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -314,18 +314,13 @@ - When system shutdown or a sleep state is requested, - ignore inhibitor locks. Applications can establish inhibitor - locks to avoid that certain important operations (such as CD - burning or suchlike) are interrupted by system shutdown or a - sleep state. Any user may take these locks and privileged - users may override these locks. If any locks are taken, - shutdown and sleep state requests will normally fail - (regardless of whether privileged or not) and a list of active locks - is printed. However, if - is specified, the locks are ignored and not printed, and the - operation attempted anyway, possibly requiring additional - privileges. + When system shutdown or a sleep state is requested, ignore inhibitor locks. Applications can establish + inhibitor locks to avoid that certain important operations (such as CD burning or suchlike) are interrupted + by system shutdown or a sleep state. Any user may take these locks and privileged users may override these + locks. If any locks are taken, shutdown and sleep state requests will normally fail (unless privileged) and a + list of active locks is printed. However, if is specified, the + established locks are ignored and not shown, and the operation attempted anyway, possibly requiring + additional privileges.