binary is executed in, and in
<citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>
which define the way the processes are
- terminated.</para>
+ terminated. Note that the User= and Group= options are
+ not particularly useful for mount units specifying a
+ <literal>Type=</literal> option or using configuration
+ not specified in <filename>/etc/fstab</filename>;
+ <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
+ will refuse options that aren't listed in
+ <filename>/etc/fstab</filename> if it is not run as
+ UID 0.</para>
<para>Mount units must be named after the mount point
directories they control. Example: the mount point
mounting. See
<citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
- <para>If an mount point is beneath another mount point
+ <para>If a mount point is beneath another mount point
in the file system hierarchy, a dependency between both
units is created automatically.</para>
should wait for a device to show up before giving up
on an entry from
<filename>/etc/fstab</filename>. Specify a time in
- seconds or explicitly specifiy a unit as
+ seconds or explicitly specify a unit as
<literal>s</literal>, <literal>min</literal>,
<literal>h</literal>, <literal>ms</literal>.</para>
<term><varname>Where=</varname></term>
<listitem><para>Takes an absolute path
of a directory of the mount point. If
- the mount point is not existing at
+ the mount point does not exist at the
time of mounting, it is created. This
string must be reflected in the unit
file name. (See above.) This option is