Lines Matching full:mount
46 symbolic links and mount traps. Mount traps are directories with
51 mount traps are created with `mkdir`. The determination of whether a
52 directory should be a mount trap is based on a master map. This master
53 map is consulted by autofs to determine which directories are mount
54 points. Mount points can be *direct*/*indirect*/*offset*.
57 If neither the *direct* or *offset* mount options are given (so the
58 mount is considered to be *indirect*), then the root directory is
59 always a regular directory, otherwise it is a mount trap when it is
62 directory is a mount trap only if the filesystem is mounted *direct*
65 Directories created in the root directory are mount traps only if the
68 Directories further down the tree depend on the *maxproto* mount
71 tree are ever mount traps, they are always regular directories. When
72 the *maxproto* is four (or three), these directories are mount traps
75 So: non-empty (i.e. non-leaf) directories are never mount traps. Empty
76 directories are sometimes mount traps, and sometimes not depending on
78 and whether the mount was *indirect* or not.
80 Mount Traps
83 A core element of the implementation of autofs is the Mount Traps
92 (potentially) a mount trap. Any access to this directory beyond a
100 automount daemon asking it to find and mount the filesystem. The
103 mount has already happened. The VFS doesn't try to mount anything but
104 follows down the mount that is already there.
106 This functionality is sufficient for some users of mount traps such
110 automount daemon would not be able to mount a filesystem on the 'trap'
135 causing the directory not be a mount trap after all.
138 lookup is the automount daemon and that the mount has been
141 caught in the mount trap.
145 be managed by the same daemon. For the daemon to be able to mount
148 the automount daemon. It must only return it when a mount has
152 mount trap, either because it is a symbolic link or because it is
160 - -ENOENT if the automount daemon failed to mount anything,
177 To determine if a mount-trap is safe for RCU-walk mode it calls
183 reason that it might not be is if an expiry of the mount is
225 it was before the mount or creation, so that any access of the name
226 will trigger normal auto-mount processing. In particular, `rmdir` and
232 directories. As lower-level directories are never mount traps, other
242 differently. The field is updated at mount time and during expire
245 during path walks prevents frequent expire and immediate mount of
249 used. To cater for this case the "`strictexpire`" autofs mount option
255 using an `ioctl` as discussed later. For a *direct* mount, autofs
256 considers if the entire mount-tree can be unmounted or not. For an
257 *indirect* mount, autofs considers each of the names in the top level
265 However, it may be used again for amd format mount maps (which are
321 be passed using the 'fd=' mount option. autofs will write
445 document `autofs-mount-control.txt`, and are summarised briefly here.
505 the UID and GID of the process which triggered that mount.
529 As mentioned, an autofs mount can enter "catatonic" mode. This
538 be treated in the same way as if they came from the daemon, so mount
550 The "ignore" mount option
553 The "ignore" mount option can be used to provide a generic indicator
554 to applications that the mount entry should be ignored when displaying
555 mount information.
557 In other OSes that provide autofs and that provide a mount list to user
558 space based on the kernel mount list a no-op mount option ("ignore" is
573 mount --make-shared /autofs/mount/point
575 The automount daemon is only able to manage a single mount location for