<term><option>fido2-rp=</option></term>
<listitem><para>Takes a string, configuring the FIDO2 Relying Party (rp) for the FIDO2 unlock
- operation. If not specified <literal>io.systemd.cryptsetup</literal> is used, except if the the LUKS2
+ operation. If not specified <literal>io.systemd.cryptsetup</literal> is used, except if the LUKS2
JSON token header contains a different value. It should normally not be necessary to override
this.</para></listitem>
</varlistentry>
<para>The <varname>HostnameSource</varname> property exposes the origin of the currently configured
hostname. One of <literal>static</literal> (set from <filename>/etc/hostname</filename>),
<literal>transient</literal> (a non-permanent hostname from an external source),
- <literal>default</literal> (the value from <filename>os-release</filename> or the the compiled-in
+ <literal>default</literal> (the value from <filename>os-release</filename> or the compiled-in
fallback).</para>
<para>The <varname>IconName</varname> property exposes the <emphasis>icon name</emphasis> following the
source to copy from — if its partition type is set to <literal>root</literal> as well. If the
declared type is <literal>usr</literal> the partition backing <filename>/usr/</filename> is used as
source to copy blocks from — if its partition type is set to <literal>usr</literal> too. The logic is
- capable of automatically tracking down the the backing partitions for encrypted and Verity-enabled
+ capable of automatically tracking down the backing partitions for encrypted and Verity-enabled
volumes. <literal>CopyBlocks=auto</literal> is useful for implementing "self-replicating" systems,
i.e. systems that are their own installer.</para>
<parameter>name</parameter> parameter otherwise. The functions
<function>sd_bus_error_set_errno()</function>, <function>sd_bus_error_set_errnof()</function> and
<function>sd_bus_error_set_errnofv()</function>, return <constant>0</constant> when the specified error
- value is <constant>0</constant>, and a a negative errno-like value corresponding to the
+ value is <constant>0</constant>, and a negative errno-like value corresponding to the
<parameter>error</parameter> parameter otherwise. If an error occurs internally, one of the negative
error values listed below will be returned.</para>
<varlistentry>
<term><varname>COREDUMP_FILENAME=</varname></term>
- <listitem><para>When the core is stored externally, the path the the core file.</para>
+ <listitem><para>When the core is stored externally, the path to the core file.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>passwd.shell.root</literal></term>
- <listitem><para>Specifies the shell binary to use for the the specified account when creating
- it. Equivalent to the credential of the same name defined for the
+ <listitem><para>Specifies the shell binary to use for the specified account when creating it.
+ Equivalent to the credential of the same name defined for the
<citerefentry><refentrytitle>systemd-sysusers.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
service.</para></listitem>
</varlistentry>
<varlistentry>
<term><literal>passwd.shell.<replaceable>user</replaceable></literal></term>
- <listitem><para>Specifies the shell binary to use for the the specified account when creating it.</para></listitem>
+ <listitem><para>Specifies the shell binary to use for the specified account when creating it.</para></listitem>
</varlistentry>
</variablelist>
in the system manager. When compiled for systems with "unmerged <filename>/usr/</filename>"
(<filename>/bin</filename> is not a symlink to <filename>/usr/bin</filename>),
<literal>:<filename>/sbin</filename>:<filename>/bin</filename></literal> is appended. In case of
- the the user manager, a different path may be configured by the distribution. It is recommended to
+ the user manager, a different path may be configured by the distribution. It is recommended to
not rely on the order of entries, and have only one program with a given name in
<varname>$PATH</varname>.</para></listitem>
</varlistentry>
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>), receiving only
the sockets configured through socket-activation from the host's namespace. In such a set-up communication within
the host's network namespace is only permitted through the activation sockets passed in while all sockets allocated
- from the service code itself will be associated with the service's own namespace, and thus possibly subject to a a
- much more restrictive configuration.</para>
+ from the service code itself will be associated with the service's own namespace, and thus possibly subject to a
+ restrictive configuration.</para>
</refsect1>
<refsect1>
if (!arg_node)
return log_oom();
- /* Remember that the the device we are about to manipulate is actually the one we
+ /* Remember that the device we are about to manipulate is actually the one we
* allocated here, and thus to increase its backing file we know what to do */
node_is_our_loop = true;
}