man/systemd.mount.xml

   1 <?xml version='1.0'?> <!--*-nxml-*-->
   2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
   3   "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
   4
   5 <!--
   6   SPDX-License-Identifier: LGPL-2.1+
   7
   8   This file is part of systemd.
   9
  10   Copyright 2010 Lennart Poettering
  11 -->
  12
  13 <refentry id="systemd.mount">
  14   <refentryinfo>
  15     <title>systemd.mount</title>
  16     <productname>systemd</productname>
  17
  18     <authorgroup>
  19       <author>
  20         <contrib>Developer</contrib>
  21         <firstname>Lennart</firstname>
  22         <surname>Poettering</surname>
  23         <email>lennart@poettering.net</email>
  24       </author>
  25     </authorgroup>
  26   </refentryinfo>
  27
  28   <refmeta>
  29     <refentrytitle>systemd.mount</refentrytitle>
  30     <manvolnum>5</manvolnum>
  31   </refmeta>
  32
  33   <refnamediv>
  34     <refname>systemd.mount</refname>
  35     <refpurpose>Mount unit configuration</refpurpose>
  36   </refnamediv>
  37
  38   <refsynopsisdiv>
  39     <para><filename><replaceable>mount</replaceable>.mount</filename></para>
  40   </refsynopsisdiv>
  41
  42   <refsect1>
  43     <title>Description</title>
  44
  45     <para>A unit configuration file whose name ends in
  46     <literal>.mount</literal> encodes information about a file system
  47     mount point controlled and supervised by systemd.</para>
  48
  49     <para>This man page lists the configuration options specific to
  50     this unit type. See
  51     <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
  52     for the common options of all unit configuration files. The common
  53     configuration items are configured in the generic [Unit] and
  54     [Install] sections. The mount specific configuration options are
  55     configured in the [Mount] section.</para>
  56
  57     <para>Additional options are listed in
  58     <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
  59     which define the execution environment the
  60     <citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
  61     program is executed in, and in
  62     <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
  63     which define the way the processes are terminated, and in
  64     <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
  65     which configure resource control settings for the processes of the
  66     service.</para>
  67
  68     <para>Note that the options <varname>User=</varname> and
  69     <varname>Group=</varname> are not useful for mount units.
  70     systemd passes two parameters to
  71     <citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>;
  72     the values of <varname>What=</varname> and <varname>Where=</varname>.
  73     When invoked in this way,
  74     <citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
  75     does not read any options from <filename>/etc/fstab</filename>, and
  76     must be run as UID 0.</para>
  77
  78     <para>Mount units must be named after the mount point directories they control. Example: the mount point <filename
  79     noindex='true'>/home/lennart</filename> must be configured in a unit file <filename>home-lennart.mount</filename>.
  80     For details about the escaping logic used to convert a file system path to a unit name, see
  81     <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.  Note that mount
  82     units cannot be templated, nor is possible to add multiple names to a mount unit by creating additional symlinks to
  83     it.</para>
  84
  85     <para>Optionally, a mount unit may be accompanied by an automount
  86     unit, to allow on-demand or parallelized mounting. See
  87     <citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
  88
  89     <para>Mount points created at runtime (independently of unit files
  90     or <filename>/etc/fstab</filename>) will be monitored by systemd
  91     and appear like any other mount unit in systemd. See
  92     <filename>/proc/self/mountinfo</filename> description in
  93     <citerefentry project='man-pages'><refentrytitle>proc</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
  94     </para>
  95
  96     <para>Some file systems have special semantics as API file systems
  97     for kernel-to-userspace and userspace-to-userspace interfaces. Some
  98     of them may not be changed via mount units, and cannot be
  99     disabled. For a longer discussion see <ulink
 100     url="https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems">API
 101     File Systems</ulink>.</para>
 102   </refsect1>
 103
 104   <refsect1>
 105     <title>Automatic Dependencies</title>
 106
 107     <refsect2>
 108       <title>Implicit Dependencies</title>
 109
 110       <para>The following dependencies are implicitly added:</para>
 111
 112       <itemizedlist>
 113         <listitem><para>If a mount unit is beneath another mount unit in the file
 114         system hierarchy, both a requirement dependency and an ordering
 115         dependency between both units are created automatically.</para></listitem>
 116
 117         <listitem><para>Block device backed file systems automatically gain
 118         <varname>BindsTo=</varname> and <varname>After=</varname> type
 119         dependencies on the device unit encapsulating the block
 120         device (see below).</para></listitem>
 121
 122         <listitem><para>If traditional file system quota is enabled for a mount
 123         unit, automatic <varname>Wants=</varname> and
 124         <varname>Before=</varname> dependencies on
 125         <filename>systemd-quotacheck.service</filename> and
 126         <filename>quotaon.service</filename> are added.</para></listitem>
 127
 128         <listitem><para>Additional implicit dependencies may be added as result of
 129         execution and resource control parameters as documented in
 130         <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 131         and
 132         <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
 133         </para></listitem>
 134       </itemizedlist>
 135     </refsect2>
 136
 137     <refsect2>
 138       <title>Default Dependencies</title>
 139
 140       <para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
 141
 142       <itemizedlist>
 143         <listitem><para>All mount units acquire automatic <varname>Before=</varname> and <varname>Conflicts=</varname> on
 144         <filename>umount.target</filename> in order to be stopped during shutdown.</para></listitem>
 145
 146         <listitem><para>Mount units referring to local file systems automatically gain
 147         an <varname>After=</varname> dependency on <filename>local-fs-pre.target</filename>.</para></listitem>
 148
 149         <listitem><para>Network mount units
 150         automatically acquire <varname>After=</varname> dependencies on <filename>remote-fs-pre.target</filename>,
 151         <filename>network.target</filename> and <filename>network-online.target</filename>. Towards the latter a
 152         <varname>Wants=</varname> unit is added as well.</para></listitem>
 153       </itemizedlist>
 154
 155       <para>Mount units referring to local and network file systems are distinguished by their file system type
 156       specification. In some cases this is not sufficient (for example network block device based mounts, such as
 157       iSCSI), in which case <option>_netdev</option> may be added to the mount option string of the unit, which forces
 158       systemd to consider the mount unit a network mount.</para>
 159     </refsect2>
 160   </refsect1>
 161
 162   <refsect1>
 163     <title><filename>fstab</filename></title>
 164
 165     <para>Mount units may either be configured via unit files, or via
 166     <filename>/etc/fstab</filename> (see
 167     <citerefentry project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 168     for details). Mounts listed in <filename>/etc/fstab</filename>
 169     will be converted into native units dynamically at boot and when
 170     the configuration of the system manager is reloaded. In general,
 171     configuring mount points through <filename>/etc/fstab</filename>
 172     is the preferred approach. See
 173     <citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 174     for details about the conversion.</para>
 175
 176     <para>The NFS mount option <option>bg</option> for NFS background mounts
 177     as documented in <citerefentry project='man-pages'><refentrytitle>nfs</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 178     is detected by <command>systemd-fstab-generator</command> and the options
 179     are transformed so that systemd fulfills the job-control implications of
 180     that option.  Specifically <command>systemd-fstab-generator</command> acts
 181     as though <literal>x-systemd.mount-timout=infinity,retry=10000</literal> was
 182     prepended to the option list, and <literal>fg,nofail</literal> was appended.
 183     Depending on specific requirements, it may be appropriate to provide some of
 184     these options explicitly, or to make use of the
 185     <literal>x-systemd.automount</literal> option described below instead
 186     of using <literal>bg</literal>.</para>
 187
 188     <para>When reading <filename>/etc/fstab</filename> a few special
 189     mount options are understood by systemd which influence how
 190     dependencies are created for mount points. systemd will create a
 191     dependency of type <varname>Wants=</varname> or
 192     <option>Requires</option> (see option <option>nofail</option>
 193     below), from either <filename>local-fs.target</filename> or
 194     <filename>remote-fs.target</filename>, depending whether the file
 195     system is local or remote.</para>
 196
 197     <variablelist class='fstab-options'>
 198
 199       <varlistentry>
 200         <term><option>x-systemd.requires=</option></term>
 201
 202         <listitem><para>Configures a <varname>Requires=</varname> and
 203         an <varname>After=</varname> dependency between the created
 204         mount unit and another systemd unit, such as a device or mount
 205         unit. The argument should be a unit name, or an absolute path
 206         to a device node or mount point.  This option may be specified
 207         more than once. This option is particularly useful for mount
 208         point declarations that need an additional device to be around
 209         (such as an external journal device for journal file systems)
 210         or an additional mount to be in place (such as an overlay file
 211         system that merges multiple mount points). See
 212         <varname>After=</varname> and <varname>Requires=</varname> in
 213         <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 214         for details.</para></listitem>
 215       </varlistentry>
 216
 217       <varlistentry>
 218         <term><option>x-systemd.before=</option></term>
 219         <term><option>x-systemd.after=</option></term>
 220
 221         <listitem><para>Configures a <varname>Before=</varname>
 222         dependency or <varname>After=</varname> between the created
 223         mount unit and another systemd unit, such as a mount unit.
 224         The argument should be a unit name or an absolute path
 225         to a mount point. This option may be specified more than once.
 226         This option is particularly useful for mount point declarations
 227         with <option>nofail</option> option that are mounted
 228         asynchronously but need to be mounted before or after some unit
 229         start, for example, before <filename>local-fs.target</filename>
 230         unit.
 231         See <varname>Before=</varname> and <varname>After=</varname> in
 232         <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 233         for details.</para></listitem>
 234       </varlistentry>
 235
 236       <varlistentry>
 237         <term><option>x-systemd.requires-mounts-for=</option></term>
 238
 239         <listitem><para>Configures a
 240         <varname>RequiresMountsFor=</varname> dependency between the
 241         created mount unit and other mount units. The argument must be
 242         an absolute path. This option may be specified more than once.
 243         See <varname>RequiresMountsFor=</varname> in
 244         <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 245         for details.</para></listitem>
 246        </varlistentry>
 247
 248       <varlistentry>
 249         <term><option>x-systemd.device-bound</option></term>
 250
 251         <listitem><para>The block device backed file system will be upgraded
 252         to <varname>BindsTo=</varname> dependency. This option is only useful
 253         when mounting file systems manually with
 254         <citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 255         as the default dependency in this case is <varname>Requires=</varname>.
 256         This option is already implied by entries in <filename>/etc/fstab</filename>
 257         or by mount units.
 258         </para></listitem>
 259       </varlistentry>
 260
 261       <varlistentry>
 262         <term><option>x-systemd.automount</option></term>
 263
 264         <listitem><para>An automount unit will be created for the file
 265         system. See
 266         <citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 267         for details.</para></listitem>
 268       </varlistentry>
 269
 270       <varlistentry>
 271         <term><option>x-systemd.idle-timeout=</option></term>
 272
 273         <listitem><para>Configures the idle timeout of the
 274         automount unit. See <varname>TimeoutIdleSec=</varname> in
 275         <citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 276         for details.</para></listitem>
 277       </varlistentry>
 278
 279       <varlistentry>
 280         <term><option>x-systemd.device-timeout=</option></term>
 281
 282         <listitem><para>Configure how long systemd should wait for a
 283         device to show up before giving up on an entry from
 284         <filename>/etc/fstab</filename>. Specify a time in seconds or
 285         explicitly append a unit such as <literal>s</literal>,
 286         <literal>min</literal>, <literal>h</literal>,
 287         <literal>ms</literal>.</para>
 288
 289         <para>Note that this option can only be used in
 290         <filename>/etc/fstab</filename>, and will be
 291         ignored when part of the <varname>Options=</varname>
 292         setting in a unit file.</para>
 293         </listitem>
 294       </varlistentry>
 295
 296       <varlistentry>
 297         <term><option>x-systemd.mount-timeout=</option></term>
 298
 299         <listitem><para>Configure how long systemd should wait for the
 300         mount command to finish before giving up on an entry from
 301         <filename>/etc/fstab</filename>. Specify a time in seconds or
 302         explicitly append a unit such as <literal>s</literal>,
 303         <literal>min</literal>, <literal>h</literal>,
 304         <literal>ms</literal>.</para>
 305
 306         <para>Note that this option can only be used in
 307         <filename>/etc/fstab</filename>, and will be
 308         ignored when part of the <varname>Options=</varname>
 309         setting in a unit file.</para>
 310
 311         <para>See <varname>TimeoutSec=</varname> below for
 312         details.</para>
 313         </listitem>
 314       </varlistentry>
 315
 316       <varlistentry>
 317         <term><option>x-systemd.makefs</option></term>
 318
 319         <listitem><para>The file system or swap structure will be initialized
 320         on the device. If the device is not "empty", i.e. it contains any signature,
 321         the operation will be skipped. It is hence expected that this option
 322         remains set even after the device has been initalized.</para>
 323
 324         <para>Note that this option can only be used in
 325         <filename>/etc/fstab</filename>, and will be ignored when part of the
 326         <varname>Options=</varname> setting in a unit file.</para>
 327
 328         <para>See
 329         <citerefentry><refentrytitle>systemd-makefs@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
 330         </para>
 331
 332         <para><citerefentry project='man-pages'><refentrytitle>wipefs</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 333         may be used to remove any signatures from a block device to force
 334         <option>x-systemd.makefs</option> to reinitialize the device.</para>
 335         </listitem>
 336       </varlistentry>
 337
 338       <varlistentry>
 339         <term><option>x-systemd.growfs</option></term>
 340
 341         <listitem><para>The file system will be grown to occupy the full block
 342         device. If the file system is already at maximum size, no action will
 343         be performed. It is hence expected that this option remains set even after
 344         the file system has been grown. Only certain file system types are supported,
 345         see
 346         <citerefentry><refentrytitle>systemd-makefs@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 347         for details.</para>
 348
 349         <para>Note that this option can only be used in
 350         <filename>/etc/fstab</filename>, and will be ignored when part of the
 351         <varname>Options=</varname> setting in a unit file.</para></listitem>
 352       </varlistentry>
 353
 354       <varlistentry>
 355         <term><option>_netdev</option></term>
 356
 357         <listitem><para>Normally the file system type is used to determine if a
 358         mount is a "network mount", i.e. if it should only be started after the
 359         network is available. Using this option overrides this detection and
 360         specifies that the mount requires network.</para>
 361
 362         <para>Network mount units are ordered between <filename>remote-fs-pre.target</filename>
 363         and <filename>remote-fs.target</filename>, instead of
 364         <filename>local-fs-pre.target</filename> and <filename>local-fs.target</filename>.
 365         They also pull in <filename>network-online.target</filename> and are ordered after
 366         it and <filename>network.target</filename>.</para>
 367         </listitem>
 368       </varlistentry>
 369
 370       <varlistentry>
 371         <term><option>noauto</option></term>
 372         <term><option>auto</option></term>
 373
 374         <listitem><para>With <option>noauto</option>, the mount unit will not be added as a dependency for
 375         <filename>local-fs.target</filename> or <filename>remote-fs.target</filename>. This means that it will not be
 376         mounted automatically during boot, unless it is pulled in by some other unit. The <option>auto</option> option
 377         has the opposite meaning and is the default. Note that the <option>noauto</option> option has an effect on the
 378         mount unit itself only — if <option>x-systemd.automount</option> is used (see above), then the matching
 379         automount unit will still be pulled in by these targets.</para>
 380         </listitem>
 381       </varlistentry>
 382
 383       <varlistentry>
 384         <term><option>nofail</option></term>
 385
 386         <listitem><para>With <option>nofail</option>, this mount will
 387         be only wanted, not required, by
 388         <filename>local-fs.target</filename> or
 389         <filename>remote-fs.target</filename>. This means that the
 390         boot will continue even if this mount point is not mounted
 391         successfully.</para>
 392         </listitem>
 393       </varlistentry>
 394
 395       <varlistentry>
 396         <term><option>x-initrd.mount</option></term>
 397
 398         <listitem><para>An additional filesystem to be mounted in the
 399         initramfs. See <filename>initrd-fs.target</filename>
 400         description in
 401         <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
 402         </para></listitem>
 403       </varlistentry>
 404     </variablelist>
 405
 406     <para>If a mount point is configured in both
 407     <filename>/etc/fstab</filename> and a unit file that is stored
 408     below <filename>/usr</filename>, the former will take precedence.
 409     If the unit file is stored below <filename>/etc</filename>, it
 410     will take precedence. This means: native unit files take
 411     precedence over traditional configuration files, but this is
 412     superseded by the rule that configuration in
 413     <filename>/etc</filename> will always take precedence over
 414     configuration in <filename>/usr</filename>.</para>
 415   </refsect1>
 416
 417   <refsect1>
 418     <title>Options</title>
 419
 420     <para>Mount files must include a [Mount] section, which carries
 421     information about the file system mount points it supervises. A
 422     number of options that may be used in this section are shared with
 423     other unit types. These options are documented in
 424     <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 425     and
 426     <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
 427     The options specific to the [Mount] section of mount units are the
 428     following:</para>
 429
 430     <variablelist class='unit-directives'>
 431
 432       <varlistentry>
 433         <term><varname>What=</varname></term>
 434         <listitem><para>Takes an absolute path of a device node, file or other resource to mount. See <citerefentry
 435         project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry> for details. If
 436         this refers to a device node, a dependency on the respective device unit is automatically created. (See
 437         <citerefentry><refentrytitle>systemd.device</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more
 438         information.) This option is mandatory. Note that the usual specifier expansion is applied to this setting,
 439         literal percent characters should hence be written as <literal>%%</literal>.</para></listitem>
 440       </varlistentry>
 441
 442       <varlistentry>
 443         <term><varname>Where=</varname></term>
 444         <listitem><para>Takes an absolute path of a directory for the
 445         mount point; in particular, the destination cannot be a symbolic
 446         link.  If the mount point does not exist at the time of
 447         mounting, it is created. This string must be reflected in the
 448         unit filename. (See above.) This option is
 449         mandatory.</para></listitem>
 450       </varlistentry>
 451
 452       <varlistentry>
 453         <term><varname>Type=</varname></term>
 454         <listitem><para>Takes a string for the file system type. See
 455         <citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 456         for details. This setting is optional.</para></listitem>
 457       </varlistentry>
 458
 459       <varlistentry>
 460         <term><varname>Options=</varname></term>
 461
 462         <listitem><para>Mount options to use when mounting. This takes a comma-separated list of options. This setting
 463         is optional. Note that the usual specifier expansion is applied to this setting, literal percent characters
 464         should hence be written as <literal>%%</literal>.</para></listitem>
 465       </varlistentry>
 466
 467       <varlistentry>
 468         <term><varname>SloppyOptions=</varname></term>
 469
 470         <listitem><para>Takes a boolean argument. If true, parsing of
 471         the options specified in <varname>Options=</varname> is
 472         relaxed, and unknown mount options are tolerated. This
 473         corresponds with
 474         <citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>'s
 475         <parameter>-s</parameter> switch. Defaults to
 476         off.</para></listitem>
 477       </varlistentry>
 478
 479       <varlistentry>
 480         <term><varname>LazyUnmount=</varname></term>
 481
 482         <listitem><para>Takes a boolean argument. If true, detach the
 483         filesystem from the filesystem hierarchy at time of the unmount
 484         operation, and clean up all references to the filesystem as
 485         soon as they are not busy anymore.
 486         This corresponds with
 487         <citerefentry project='man-pages'><refentrytitle>umount</refentrytitle><manvolnum>8</manvolnum></citerefentry>'s
 488         <parameter>-l</parameter> switch. Defaults to
 489         off.</para></listitem>
 490       </varlistentry>
 491
 492       <varlistentry>
 493         <term><varname>ForceUnmount=</varname></term>
 494
 495         <listitem><para>Takes a boolean argument. If true, force an
 496         unmount (in case of an unreachable NFS system).
 497         This corresponds with
 498         <citerefentry project='man-pages'><refentrytitle>umount</refentrytitle><manvolnum>8</manvolnum></citerefentry>'s
 499         <parameter>-f</parameter> switch. Defaults to
 500         off.</para></listitem>
 501       </varlistentry>
 502
 503       <varlistentry>
 504         <term><varname>DirectoryMode=</varname></term>
 505         <listitem><para>Directories of mount points (and any parent
 506         directories) are automatically created if needed. This option
 507         specifies the file system access mode used when creating these
 508         directories. Takes an access mode in octal notation. Defaults
 509         to 0755.</para></listitem>
 510       </varlistentry>
 511
 512       <varlistentry>
 513         <term><varname>TimeoutSec=</varname></term>
 514         <listitem><para>Configures the time to wait for the mount
 515         command to finish. If a command does not exit within the
 516         configured time, the mount will be considered failed and be
 517         shut down again. All commands still running will be terminated
 518         forcibly via <constant>SIGTERM</constant>, and after another
 519         delay of this time with <constant>SIGKILL</constant>. (See
 520         <option>KillMode=</option> in
 521         <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>.)
 522         Takes a unit-less value in seconds, or a time span value such
 523         as "5min 20s". Pass 0 to disable the timeout logic. The
 524         default value is set from the manager configuration file's
 525         <varname>DefaultTimeoutStartSec=</varname>
 526         variable.</para></listitem>
 527       </varlistentry>
 528     </variablelist>
 529
 530     <para>Check
 531     <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 532     and
 533     <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>
 534     for more settings.</para>
 535   </refsect1>
 536
 537   <refsect1>
 538       <title>See Also</title>
 539       <para>
 540         <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
 541         <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
 542         <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
 543         <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
 544         <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
 545         <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
 546         <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
 547         <citerefentry><refentrytitle>systemd.device</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
 548         <citerefentry project='man-pages'><refentrytitle>proc</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
 549         <citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
 550         <citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
 551         <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>
 552       </para>
 553   </refsect1>
 554
 555 </refentry>