X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemctl.xml;h=632a26dedbd12febdf855567ff9bdbcfcb1b90b1;hb=409dee2e44e7dc73d6bf00d782938e4cb4105f5b;hp=1bd4af33867fe33b3f639ffd302b4c8d06b8548e;hpb=991f2a3932e831ccac609ba88f6e725b6c01acfe;p=elogind.git

diff --git a/man/systemctl.xml b/man/systemctl.xml
index 1bd4af338..632a26ded 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -92,7 +92,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
         <term><option>--type=</option></term>
 
         <listitem>
-          <para>The argument should be a comma separated list of unit
+          <para>The argument should be a comma-separated list of unit
           types such as <option>service</option> and
           <option>socket</option>, or unit load states such as
           <option>loaded</option> and <option>masked</option>
@@ -122,7 +122,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
           <command>show</command> command, limit display to certain
           properties as specified as argument. If not specified all
           set properties are shown. The argument should be a
-          comma-seperated list of property names, such as
+          comma-separated list of property names, such as
           <literal>MainPID</literal>. If specified more than once all
           properties with the specified names are shown.</para>
         </listitem>
@@ -133,10 +133,35 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
         <term><option>--all</option></term>
 
         <listitem>
-          <para>When listing units, show all units, regardless of
-          their state, including inactive units. When showing
+          <para>When listing units, show all loaded units, regardless
+          of their state, including inactive units. When showing
           unit/job/manager properties, show all properties regardless
           whether they are set or not.</para>
+          <para>To list all units installed on the system, use the
+          <command>list-unit-files</command> command instead.</para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>--reverse</option></term>
+
+        <listitem>
+          <para>Show reverse dependencies between units with
+          <command>list-dependencies</command>, i.e. units with
+          dependencies of type <varname>Wants=</varname> or
+          <varname>Requires=</varname> on the given unit.
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>--after</option></term>
+        <term><option>--before</option></term>
+
+        <listitem>
+          <para>Show which units are started after, resp. before
+          with <command>list-dependencies</command>.
+          </para>
         </listitem>
       </varlistentry>
 
@@ -150,6 +175,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
       </varlistentry>
 
       <varlistentry>
+        <term><option>-l</option></term>
         <term><option>--full</option></term>
 
         <listitem>
@@ -356,8 +382,8 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
         <listitem>
           <para>When used with <command>kill</command>, choose which
           signal to send to selected processes. Must be one of the
-          well known signal specifiers such as SIGTERM, SIGINT or
-          SIGSTOP. If omitted defaults to
+          well known signal specifiers such as <constant>SIGTERM</constant>, <constant>SIGINT</constant> or
+          <constant>SIGSTOP</constant>. If omitted defaults to
           <option>SIGTERM</option>.</para>
         </listitem>
       </varlistentry>
@@ -427,7 +453,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
 
         <listitem>
           <para>Execute operation remotely. Specify a hostname, or
-          username and hostname separated by @, to connect to. This
+          username and hostname separated by <literal>@</literal>, to connect to. This
           will use SSH to talk to the remote systemd
           instance.</para>
         </listitem>
@@ -468,6 +494,15 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
         </listitem>
       </varlistentry>
 
+      <varlistentry>
+        <term><option>--plain</option></term>
+
+        <listitem>
+          <para>When used with <command>list-dependencies</command>
+          the output is printed as a list instead of a tree.</para>
+        </listitem>
+      </varlistentry>
+
     </variablelist>
   </refsect1>
 
@@ -512,6 +547,19 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
         </listitem>
       </varlistentry>
 
+       <varlistentry>
+         <term><command>set-log-level <replaceable>LEVEL</replaceable></command></term>
+
+         <listitem>
+           <para>Change current log level of the
+           <command>systemd</command> daemon to
+           <replaceable>LEVEL</replaceable> (accepts the same values
+           as <option>--log-level=</option> described in
+           <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>).
+           </para>
+         </listitem>
+      </varlistentry>
+
       <varlistentry>
         <term><command>start <replaceable>NAME</replaceable>...</command></term>
 
@@ -684,7 +732,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
           names such as <literal>cpu.shares</literal>. This will
           output the current values of the specified attributes,
           separated by new-lines. For attributes that take list of
-          items the output will be new-line separated, too. This
+          items the output will be new-line-separated, too. This
           operation will always try to retrieve the data in question
           from the kernel first, and if that is not available use the
           configured values instead. Instead of low-level control
@@ -755,7 +803,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
         unit name, plus a control group specification in the syntax
         <replaceable>CONTROLLER</replaceable>:<replaceable>PATH</replaceable>
         or <replaceable>CONTROLLER</replaceable>. In the latter syntax
-        (where the path is ommitted) the default unit control group
+        (where the path is omitted) the default unit control group
         path is implied. Examples: <literal>cpu</literal> or
         <literal>cpu:/foo/bar</literal>. If a unit is removed from a
         control group hierarchy all its processes will be moved to the
@@ -963,6 +1011,24 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
         </listitem>
       </varlistentry>
 
+      <varlistentry>
+        <term><command>get-default</command></term>
+
+        <listitem>
+          <para>Get the default target specified
+          via <filename>default.target</filename> link.</para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><command>set-default <replaceable>NAME</replaceable></command></term>
+
+        <listitem>
+          <para>Set the default target to boot into. Command links
+          <filename>default.target</filename> to the given unit.</para>
+        </listitem>
+      </varlistentry>
+
       <varlistentry>
         <term><command>load <replaceable>NAME</replaceable>...</command></term>