diff options
| -rw-r--r-- | man/systemd.automount.xml | 14 | ||||
| -rw-r--r-- | man/systemd.mount.xml | 13 |
2 files changed, 14 insertions, 13 deletions
diff --git a/man/systemd.automount.xml b/man/systemd.automount.xml index da35a7d26b..513f939dd2 100644 --- a/man/systemd.automount.xml +++ b/man/systemd.automount.xml @@ -39,13 +39,13 @@ [Install] sections. The automount specific configuration options are configured in the [Automount] section.</para> - <para>Automount units must be named after the automount directories they control. Example: the automount point - <filename index="false">/home/lennart</filename> must be configured in a unit file - <filename>home-lennart.automount</filename>. For details about the escaping logic used to convert a file system - path to a unit name see - <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Note that - automount units cannot be templated, nor is it possible to add multiple names to an automount unit by creating - additional symlinks to its unit file.</para> + <para>Automount units must be named after the automount directories they control. Example: the automount + point <filename index="false">/home/lennart</filename> must be configured in a unit file + <filename>home-lennart.automount</filename>. For details about the escaping logic used to convert a file + system path to a unit name see + <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Note + that automount units cannot be templated, nor is it possible to add multiple names to an automount unit + by creating symlinks to its unit file.</para> <para>For each automount unit file a matching mount unit file (see <citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry> diff --git a/man/systemd.mount.xml b/man/systemd.mount.xml index 6d21d32778..8f4ebfc788 100644 --- a/man/systemd.mount.xml +++ b/man/systemd.mount.xml @@ -59,12 +59,13 @@ does not read any options from <filename>/etc/fstab</filename>, and must be run as UID 0.</para> - <para>Mount units must be named after the mount point directories they control. Example: the mount point <filename - index="false">/home/lennart</filename> must be configured in a unit file <filename>home-lennart.mount</filename>. - For details about the escaping logic used to convert a file system path to a unit name, see - <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Note that mount - units cannot be templated, nor is possible to add multiple names to a mount unit by creating additional symlinks to - it.</para> + <para>Mount units must be named after the mount point directories they control. Example: the mount point + <filename index="false">/home/lennart</filename> must be configured in a unit file + <filename>home-lennart.mount</filename>. For details about the escaping logic used to convert a file + system path to a unit name, see + <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Note + that mount units cannot be templated, nor is possible to add multiple names to a mount unit by creating + symlinks to its unit file.</para> <para>Optionally, a mount unit may be accompanied by an automount unit, to allow on-demand or parallelized mounting. See |