Lines Matching full:it
5 autofs - how it works
61 always a regular directory, otherwise it is a mount trap when it is
71 option and particularly whether it is less than five or not.
93 the inode has S_AUTOMOUNT set, or can be set directly) then it is
97 should be mounted on the directory and to return it. The VFS is
102 automount daemon asking it to find and mount the filesystem. The
104 everything is ready. It will then return "`NULL`" indicating that the
110 reflected on the client. However it is not sufficient for autofs. As
124 to `false`. It may return one of three things:
139 autofs returns this if it detects that the process performing the
141 requested but has not yet completed. How it determines this is
145 There is a subtlety here. It is possible that a second autofs
148 something on the second it must be able to "walk" down past the
150 the automount daemon. It must only return it when a mount has
154 mount trap, either because it is a symbolic link or because it is
163 - -ENOMEM if it ran out of memory,
173 filename path (i.e. it is like running on tip-toes). RCU-walk cannot
174 cope with all situations so when it finds a difficulty it falls back
179 To determine if a mount-trap is safe for RCU-walk mode it calls
183 spinlocks if at all possible. Its sole purpose is to determine if it
185 reason that it might not be is if an expiry of the mount is
191 mounted, it *will* fall back to REF-walk. `d_manage()` cannot make the
192 VFS remain in RCU-walk mode, but can only tell it to get out of
196 -ECHILD if there is any reason to believe it is unsafe to enter the
197 mounted filesystem, otherwise it should return 0.
200 initiated or is being considered, otherwise it returns 0.
207 much as it can expire any unused dentry information from the dcache.
211 mounting to the automount daemon, it must involve the automount daemon
225 symbolic links or empty directories any time it likes. If the unmount
227 it was before the mount or creation, so that any access of the name
236 unmounted. So it is generally safest to use the autofs expiry
241 time stamp on each directory or symlink. For symlinks it genuinely
243 out where it points to. For directories the field is used slightly
245 checks if it is found to be in use (ie. open file descriptor or
267 However, it may be used again for amd format mount maps (which are
272 When autofs considers a directory it checks the `last_used` time and
273 compares it with the "timeout" value set when the filesystem was
274 mounted, though this check is ignored in some cases. It also checks if
275 the directory or anything below it is in use. For symbolic links,
283 mounts. If it finds something in the root directory to expire it will
292 indirect mounts. If it selects an object to expire, it will notify
349 access it but it isn't there) or that it has been selected for expiry.
358 "expiring" and other accesses to it block until the message is
377 mode meaning that it stops sending notifications to the daemon.
406 **AUTOFS_IOC_EXPIRE** except that it causes notification to be
407 sent to the daemon, and it blocks until the daemon acknowledges.
415 that the daemon has requested this because it is capable of
424 It is not always possible to open the root of an autofs filesystem,
426 is restarted there is no way for it to regain control of existing
430 It requires CAP_SYS_ADMIN for access.
509 happens if a write to the notification pipe fails, or if it is
539 system users can optionally use it.
547 With bind mounts and name spaces it is possible for an autofs