<refsect1>
<title>Notes</title>
- <para>These commands are implemented in a way that preserves compatiblity with
+ <para>These commands are implemented in a way that preserves compatibility with
the original SysV commands.
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
verbs <command>halt</command>, <command>poweroff</command>,
<programlisting>journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097 + _SYSTEMD_UNIT=dbus.service</programlisting>
- <para>To show all fields emited <emphasis>by</emphasis> a unit and <emphasis>about</emphasis>
+ <para>To show all fields emitted <emphasis>by</emphasis> a unit and <emphasis>about</emphasis>
the unit, option <option>-u</option>/<option>--unit=</option> should be used.
<command>journalctl -u <replaceable>name</replaceable></command>
expands to a complex filter similar to
<title>Initialization</title>
<para>Each machine should have a non-empty ID in normal operation. The ID of each
- machine should be unique. To achive those objectives,
+ machine should be unique. To achieve those objectives,
<filename>/etc/machine-id</filename> can be initialized in a few different ways.
</para>
to be bind-mounted over the real file, in case the image is used read-only.</para>
<para><citerefentry><refentrytitle>systemd-firstboot</refentrytitle><manvolnum>1</manvolnum></citerefentry>
- may be used to to initialize <filename>/etc/machine-id</filename> on mounted (but not
+ may be used to initialize <filename>/etc/machine-id</filename> on mounted (but not
booted) system images.</para>
<para>When a machine is booted with
<listitem><para>When used with <command>bind</command>, creates the destination file or directory before
applying the bind mount. Note that even though the name of this option suggests that it is suitable only for
- directories, this option also creates the destination file node to mount over if the the object to mount is not
+ directories, this option also creates the destination file node to mount over if the object to mount is not
a directory, but a regular file, device node, socket or FIFO.</para></listitem>
</varlistentry>
<listitem>
<para>Show discovered LLDP (Link Layer Discovery Protocol) neighbors. If one or more link names are specified
only neighbors on those interfaces are shown. Otherwise shows discovered neighbors on all interfaces. Note
- that for this feature to work, <varname>LLDP=</varname> must be turned on on the specific interface, see
+ that for this feature to work, <varname>LLDP=</varname> must be turned on for the specific interface, see
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
details.</para>
<para>By default all unit files whose names start with a prefix generated from the image's file name are copied
out. Specifically, the prefix is determined from the image file name with any suffix such as
- <filename>.raw</filename> removed, truncated at the first occurence of and underscore character
+ <filename>.raw</filename> removed, truncated at the first occurrence of and underscore character
(<literal>_</literal>), if there is one. The underscore logic is supposed to be used to versioning so that the
an image file <filename>foobar_47.11.raw</filename> will result in a unit file matching prefix of
<filename>foobar</filename>. This prefix is then compared with all unit files names contained in the image in
</row>
<row>
<entry><option>attached-runtime</option></entry>
- <entry>Like <option>attached</option>, but the the unit files have been made available transiently only, i.e. the <command>attach</command> command has been invoked with the <option>--runtime</option> option.</entry>
+ <entry>Like <option>attached</option>, but the unit files have been made available transiently only, i.e. the <command>attach</command> command has been invoked with the <option>--runtime</option> option.</entry>
</row>
<row>
<entry><option>enabled</option></entry>
<term><command>remove</command> <replaceable>IMAGE</replaceable>…</term>
<listitem><para>Removes one or more portable service images. Note that this command will only remove the
- specified image path itself — it it refers to a symbolic link then the symbolic link is removed and not the
+ specified image path itself — it refers to a symbolic link then the symbolic link is removed and not the
image it points to.</para></listitem>
</varlistentry>
<para><function>sd_bus_request_name()</function> operates in a synchronous fashion: a message requesting the name
is sent to the bus broker, and the call waits until the broker responds.</para>
- <para><function>sd_bus_request_name_async()</function> is an asynchronous version of of
+ <para><function>sd_bus_request_name_async()</function> is an asynchronous version of
<function>sd_bus_release_name()</function>. Instead of waiting for the request to complete, the request message is
enqueued. The specified <parameter>callback</parameter> will be called when the broker's response is received. If
the parameter is specified as <constant>NULL</constant> a default implementation is used instead which will
itself and is freed automatically when the bus object is freed. Regular (i.e. non-floating) bus slot objects keep
the bus referenced, hence the bus object remains allocated at least as long as there remains at least one
referenced bus slot object around. The floating state hence controls the direction of referencing between the bus
- object and the bus slot objects: if floating the bus pins the the bus slot, and otherwise the bus slot pins the bus
+ object and the bus slot objects: if floating the bus pins the bus slot, and otherwise the bus slot pins the bus
objects. Use <function>sd_bus_slot_set_floating()</function> to switch between both modes: if the
<parameter>b</parameter> parameter is zero, the slot object is considered floating, otherwise it is made a regular
(non-floating) slot object.</para>
journal, to read the newly added entries.</para></listitem>
<listitem><para>If <constant>SD_JOURNAL_INVALIDATE</constant>, journal files were added to or removed from the
- set of of journal files watched (e.g. due to rotation or vacuuming), and thus entries might have appeared or
+ set of journal files watched (e.g. due to rotation or vacuuming), and thus entries might have appeared or
disappeared at arbitrary places in the log stream, possibly before or after the previous end of the log
stream. If <constant>SD_JOURNAL_INVALIDATE</constant> is returned, live-view UIs that want to reflect on screen
the precise state of the log data on disk should probably refresh their entire display (relative to the cursor of
- the log entry on the top of the screen). Programs only interested in a strictly sequencial stream of log data may
+ the log entry on the top of the screen). Programs only interested in a strictly sequential stream of log data may
treat <constant>SD_JOURNAL_INVALIDATE</constant> the same way as <constant>SD_JOURNAL_APPEND</constant>, thus
ignoring any changes to the log view earlier than the old end of the log stream.</para></listitem>
</itemizedlist>
... some override from another package
# /etc/systemd/logind.conf.d/50-override.conf
-... some adminstrator override
+... some administrator override
</programlisting>
</example>
in <citerefentry project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
see <citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
They are instantiated for each device for which the file system or swap structure
- needs to be initalized, and for each mount point where the file system needs to
+ needs to be initialized, and for each mount point where the file system needs to
be grown.</para>
<para>These services are started at boot, either right before or right after the
all mount units that mount and failed are kept in memory until the user explicitly resets their failure state with
<command>systemctl reset-failed</command> or an equivalent command. On the other hand, units that stopped
successfully are unloaded immediately. If this option is turned on the "garbage collection" of units is more
- agressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for
+ aggressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for
<command>--property=CollectMode=inactive-or-failed</command>, see the explanation for
<varname>CollectMode=</varname> in
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for further
<replaceable>LIMIT</replaceable> should refer to a resource limit type, such as
<constant>RLIMIT_NOFILE</constant> or <constant>RLIMIT_NICE</constant>. The <replaceable>SOFT</replaceable> and
<replaceable>HARD</replaceable> fields should refer to the numeric soft and hard resource limit values. If the
- second form is used, <replaceable>VALUE</replaceable> may specifiy a value that is used both as soft and hard
+ second form is used, <replaceable>VALUE</replaceable> may specify a value that is used both as soft and hard
limit. In place of a numeric value the special string <literal>infinity</literal> may be used to turn off
resource limiting for the specific type of resource. This command line option may be used multiple times to
- control limits on multiple limit types. If used multiple times for the same limit type, the last last use
+ control limits on multiple limit types. If used multiple times for the same limit type, the last use
wins. For details about resource limits see <citerefentry
project='man-pages'><refentrytitle>setrlimit</refentrytitle><manvolnum>2</manvolnum></citerefentry>. By default
resource limits for the container's init process (PID 1) are set to the same values the Linux kernel originally
are still visible by combining with <varname>BindPaths=</varname> or <varname>BindReadOnlyPaths=</varname>.</para>
<para>Setting this to <literal>yes</literal> is mostly equivalent to set the three directories in
- <varname>InaccessiblePaths=</varname>. Similary, <literal>read-only</literal> is mostly equivalent to
+ <varname>InaccessiblePaths=</varname>. Similarly, <literal>read-only</literal> is mostly equivalent to
<varname>ReadOnlyPaths=</varname>, and <literal>tmpfs</literal> is mostly equivalent to
<varname>TemporaryFileSystem=</varname>.</para>
<varlistentry>
<term><varname>ProtectKernelModules=</varname></term>
- <listitem><para>Takes a boolean argument. If true, explicit module loading will be denied. This allows to turn
- off module load and unload operations on modular kernels. It is recommended to turn this on for most services
+ <listitem><para>Takes a boolean argument. If true, explicit module loading will be denied. This allows
+ module load and unload operations to be turned off on modular kernels. It is recommended to turn this on for most services
that do not need special file systems or extra kernel modules to work. Defaults to off. Enabling this option
removes <constant>CAP_SYS_MODULE</constant> from the capability bounding set for the unit, and installs a
system call filter to block module system calls, also <filename>/usr/lib/modules</filename> is made
<para><varname>StandardInputText=</varname> accepts arbitrary textual data. C-style escapes for special
characters as well as the usual <literal>%</literal>-specifiers are resolved. Each time this setting is used
- the the specified text is appended to the per-unit data buffer, followed by a newline character (thus every use
+ the specified text is appended to the per-unit data buffer, followed by a newline character (thus every use
appends a new line to the end of the buffer). Note that leading and trailing whitespace of lines configured
with this option is removed. If an empty line is specified the buffer is cleared (hence, in order to insert an
empty line, add an additional <literal>\n</literal> to the end or beginning of a line).</para>
details. By default no filtering is applied (i.e. the default maximum log level is <option>debug</option>). Use
this option to configure the logging system to drop log messages of a specific service above the specified
level. For example, set <varname>LogLevelMax=</varname><option>info</option> in order to turn off debug logging
- of a particularly chatty unit. Note that the the configured level is applied to any log messages written by any
+ of a particularly chatty unit. Note that the configured level is applied to any log messages written by any
of the processes belonging to this unit, sent via any supported logging protocol. The filtering is applied
early in the logging pipeline, before any kind of further processing is done. Moreover, messages which pass
through this filter successfully might still be dropped by filters applied at a later stage in the logging
<varlistentry>
<term><option>x-systemd.makefs</option></term>
- <listitem><para>The file system or swap structure will be intialized
+ <listitem><para>The file system or swap structure will be initialized
on the device. If the device is not "empty", i.e. it contains any signature,
the operation will be skipped. It is hence expected that this option
remains set even after the device has been initalized.</para>
<literal>.d/</literal> subdirectory (e.g. <literal>foo@.service.d/</literal>) and the <literal>.conf</literal>
files there. Moreover for units names containing dashes (<literal>-</literal>), the set of directories generated by
truncating the unit name after all dashes is searched too. Specifically, for a unit name
- <filename>foo-bar-baz.service</filename> not only the the regular drop-in directory
+ <filename>foo-bar-baz.service</filename> not only the regular drop-in directory
<filename>foo-bar-baz.service.d/</filename> is searched but also both <filename>foo-bar-.service.d/</filename> and
<filename>foo-.service.d/</filename>. This is useful for defining common drop-ins for a set of related units, whose
names begin with a common prefix. This scheme is particularly useful for mount, automount and slice units, whose
activation may either never fail, or may succeed only a single time.</para>
<para>When a unit is unloaded due to the garbage collection logic (see above) its rate limit counters are
- flushed out too. This means that configuring start rate limiting for a unit that is not referenced continously
+ flushed out too. This means that configuring start rate limiting for a unit that is not referenced continuously
has no effect.</para></listitem>
</varlistentry>
<para>Note: <varname>Triggers=</varname> is created implicitly between a socket,
path unit, or an automount unit, and the unit they activate. By default a unit
- with the same name is triggered, but this can be overriden using
+ with the same name is triggered, but this can be overridden using
<varname>Sockets=</varname>, <varname>Service=</varname>, and <varname>Unit=</varname>
settings. See
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
projects / thirdparty / systemd.git / commitdiff
