<listitem>
<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>
- (types and states can be mixed).</para>
+ <option>socket</option>.
+ </para>
<para>If one of the arguments is a unit type, when listing
units, limit display to certain unit types. Otherwise, units
of all types will be shown.</para>
- <para>If one of the arguments is a unit load state, when
- listing units, limit display to certain unit
- types. Otherwise, units of in all load states will be
- shown.</para>
-
<para>As a special case, if one of the arguments is
<option>help</option>, a list of allowed values will be
printed and the program will exit.</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--state=</option></term>
+
+ <listitem>
+ <para>The argument should be a comma-separated list of unit LOAD
+ or SUB or ACTIVE states. When listing units, show only those
+ with specified LOAD or SUB or ACTIVE state.</para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><option>-p</option></term>
<term><option>--property=</option></term>
</listitem>
</varlistentry>
- <varlistentry>
- <term><option>--failed</option></term>
-
- <listitem>
- <para>When listing units, show only failed units. Do not
- confuse with <option>--fail</option>.</para>
- </listitem>
- </varlistentry>
-
<varlistentry>
<term><option>-l</option></term>
<term><option>--full</option></term>
is lost on reboot, the changes are lost too.</para>
<para>Similar, when used with
- <command>set-cgroup-attr</command>,
- <command>unset-cgroup-attr</command>,
- <command>set-cgroup</command> and
- <command>unset-cgroup</command>, make changes only
+ <command>set-property</command>, make changes only
temporarily, so that they are lost on the next
reboot.</para>
</listitem>
</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>
</varlistentry>
<varlistentry>
- <term><command>get-cgroup-attr <replaceable>NAME</replaceable> <replaceable>ATTRIBUTE</replaceable>...</command></term>
+ <term><command>set-property <replaceable>NAME</replaceable> <replaceable>ASSIGNMENT</replaceable>...</command></term>
<listitem>
- <para>Retrieve the specified control group attributes of the
- specified unit. Takes a unit name and one or more attribute
- 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 a list of
- items, the output will be newline-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
- group attribute names, high-level pretty names may be used,
- as used for unit execution environment configuration, see
- <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
- for details. For example, passing
- <literal>memory.limit_in_bytes</literal> and
- <literal>MemoryLimit</literal> is equivalent.</para>
- </listitem>
- </varlistentry>
+ <para>Set the specified unit properties at runtime where
+ this is supported. This allows changing configuration
+ parameter properties such as resource management controls at
+ runtime. Not all properties may be changed at runtime, but
+ many resource management settings (primarily those in
+ <citerefentry><refentrytitle>systemd.cgroup</refentrytitle><manvolnum>5</manvolnum></citerefentry>)
+ may. The changes are applied instantly, and stored on disk
+ for future boots, unless <option>--runtime</option> is
+ passed, in which case the settings only apply until the next
+ reboot. The syntax of the property assignment follows
+ closely the syntax of assignments in unit files.</para>
- <varlistentry>
- <term><command>set-cgroup-attr <replaceable>NAME</replaceable> <replaceable>ATTRIBUTE</replaceable> <replaceable>VALUE</replaceable>...</command></term>
+ <para>Example: <command>systemctl set-property foobar.service CPUShares=777</command></para>
- <listitem>
- <para>Set the specified control group attribute of the
- specified unit to the specified value. Takes a unit
- name and an attribute name such as
- <literal>cpu.shares</literal>, plus one or more values
- (multiple values may only be used for attributes that take
- multiple values). This operation will immediately update the
- kernel attribute for this unit and persistently store this
- setting for later reboots (unless <option>--runtime</option>
- is passed, in which case the setting is not saved
- persistently and only valid until the next reboot.) Instead
- of low-level control group attribute names, high-level pretty
- names may be used, as used for unit execution environment
- configuration, see
- <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
- for details. For example, passing
- <literal>memory.limit_in_bytes</literal> and
- <literal>MemoryLimit</literal> is equivalent. This operation
- will implicitly create a control group for the unit in the
- controller the attribute belongs to, if needed. For
- attributes that take multiple values, this operation will
- append the specified values to the previously set values
- list (use <command>unset-cgroup-attr</command> to reset the
- list explicitly). For attributes that take a single value
- only, the list will be reset implicitly.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><command>unset-cgroup-attr <replaceable>NAME</replaceable> <replaceable>ATTRIBUTE</replaceable>...</command></term>
-
- <listitem><para>Unset the specified control group attributes
- of the specified unit. Takes a unit name and one or more
- attribut names such as <literal>cpu.shares</literal>. This
- operation might or might not have an immediate effect on the
- current kernel attribute value. This will remove any
- persistently stored configuration values for this attribute
- (as set with <command>set-cgroup-attr</command> before),
- unless <option>--runtime</option> is passed, in which case the
- configuration is reset only until the next reboot. Again,
- high-level control group attributes may be used instead of the
- low-level kernel ones. For attributes which take multiple
- values, all currently set values are reset.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><command>set-cgroup <replaceable>NAME</replaceable> <replaceable>CGROUP</replaceable>...</command></term>
- <term><command>unset-cgroup <replaceable>NAME</replaceable> <replaceable>CGROUP</replaceable>...</command></term>
-
- <listitem><para>Add or remove a unit to/from a specific
- control group hierarchy and/or control group path. Takes a
- 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 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
- root group of the hierarchy and all control group attributes
- will be reset. These operations are immediately reflected in
- the kernel hierarchy, and stored persistently to disk (unless
- <option>--runtime</option> is passed).</para>
+ <para>Note that this command allows changing multiple
+ properties at the same time, which is preferable over
+ setting them individually. Like unit file configuration
+ settings, assigning the empty list to list parameters will
+ reset the list.</para>
</listitem>
</varlistentry>
</listitem>
</varlistentry>
- <varlistentry>
- <term><command>load <replaceable>NAME</replaceable>...</command></term>
-
- <listitem>
- <para>Load one or more units specified on the command
- line. This will simply load their configuration from disk,
- but not start them. To start them, you need to use the
- <command>start</command> command which will implicitly load
- a unit that has not been loaded yet. Note that systemd
- garbage collects loaded units that are not active or
- referenced by an active unit. This means that units loaded
- this way will usually not stay loaded for long. Also note
- that this command cannot be used to reload unit
- configuration. Use the <command>daemon-reload</command>
- command for that. All in all, this command is of little use
- except for debugging.</para>
-
- <para>This command should not be confused with the
- <command>daemon-reload</command> or
- <command>reload</command>.</para>
- </listitem>
- </varlistentry>
<varlistentry>
<term><command>list-jobs</command></term>
all pending jobs.</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term><command>dump</command></term>
- <listitem>
- <para>Dump server status. This will output a (usually very
- long) human readable manager status dump. Its format is
- subject to change without notice and should not be parsed by
- applications.</para>
- </listitem>
- </varlistentry>
<varlistentry>
<term><command>list-dependencies <replaceable>NAME</replaceable></command></term>
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>loginctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
+ <citerefentry><refentrytitle>systemd.cgroupq</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry><refentrytitle>wall</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>
~ianmdlvl / elogind.git / blobdiff