chiark / gitweb /
sd-messages.h: add new bootchart message id
[elogind.git] / man / systemctl.xml
index 97bc47ce241b261f93a2410f48491daec61f7ba7..a2c3501ec206e886cc27a5a6d8a55b27a0b08c0b 100644 (file)
@@ -172,6 +172,14 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
         </listitem>
       </varlistentry>
 
+      <varlistentry>
+        <term><option>--show-types</option></term>
+
+        <listitem>
+          <para>When showing sockets, show the type of the socket.</para>
+        </listitem>
+      </varlistentry>
+
       <varlistentry>
         <term><option>--irreversible</option></term>
 
@@ -479,6 +487,31 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
           <para>This is the default command.</para>
         </listitem>
       </varlistentry>
+
+      <varlistentry>
+        <term><command>list-sockets</command></term>
+
+        <listitem>
+          <para>List socket units ordered by the listening address. Produces output
+          similar to
+          <programlisting>
+LISTEN           UNIT                        ACTIVATES
+/dev/initctl     systemd-initctl.socket      systemd-initctl.service
+...
+[::]:22          sshd.socket                 sshd.service
+kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
+
+5 sockets listed.
+          </programlisting>
+          Note: because the addresses might contains spaces, this output
+          is not suitable for programatic consumption.
+          </para>
+
+          <para>See also the options <option>--show-types</option>,
+          <option>--all</option>, and <option>--failed</option>.</para>
+        </listitem>
+      </varlistentry>
+
       <varlistentry>
         <term><command>start <replaceable>NAME</replaceable>...</command></term>
 
@@ -722,7 +755,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
         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