X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.mount.xml;h=2dc095e47b3fa5e1d18ab0cdcc811fb69e0079f6;hp=219ef6531e2e7f87b650d1c22ee8959c113bc2ef;hb=9cc2c8b763fb4b9ddda95756a727a438a0d2a012;hpb=f848f8d87e3aafa514e8134e3ecf2317d89420e0
diff --git a/man/systemd.mount.xml b/man/systemd.mount.xml
index 219ef6531..2dc095e47 100644
--- a/man/systemd.mount.xml
+++ b/man/systemd.mount.xml
@@ -75,7 +75,14 @@
binary is executed in, and in
systemd.kill5
which define the way the processes are
- terminated.
+ terminated. Note that the User= and Group= options are
+ not particularly useful for mount units specifying a
+ Type= option or using configuration
+ not specified in /etc/fstab;
+ mount8
+ will refuse options that aren't listed in
+ /etc/fstab if it is not run as
+ UID 0.
Mount units must be named after the mount point
directories they control. Example: the mount point
@@ -95,10 +102,18 @@
in the file system hierarchy, a dependency between both
units is created automatically.
- Mount points created at runtime independent on
- unit files or /etc/fstab will be
+ Mount points created at runtime (independently of
+ unit files or /etc/fstab) will be
monitored by systemd and appear like any other mount
unit in systemd.
+
+ Some file systems have special semantics as API
+ file systems for kernel-to-userspace and
+ userspace-to-userpace interfaces. Some of them may not
+ be changed via mount units, and cannot be disabled.
+ For a longer discussion see API
+ File Systems.
@@ -275,7 +290,8 @@
systemd.service5,
systemd.device5,
mount8,
- systemd-fstab-generator8
+ systemd-fstab-generator8,
+ systemd.directives7