Lines Matching full:it
2 autofs - how it works
59 always a regular directory, otherwise it is a mount trap when it is
69 option and particularly whether it is less than five or not.
91 the inode has S_AUTOMOUNT set, or can be set directly) then it is
95 should be mounted on the directory and to return it. The VFS is
100 automount daemon asking it to find and mount the filesystem. The
102 everything is ready. It will then return "`NULL`" indicating that the
108 reflected on the client. However it is not sufficient for autofs. As
122 to `false`. It may return one of three things:
137 autofs returns this if it detects that the process performing the
139 requested but has not yet completed. How it determines this is
143 There is a subtlety here. It is possible that a second autofs
146 something on the second it must be able to "walk" down past the
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
161 - -ENOMEM if it ran out of memory,
171 filename path (i.e. it is like running on tip-toes). RCU-walk cannot
172 cope with all situations so when it finds a difficulty it falls back
177 To determine if a mount-trap is safe for RCU-walk mode it calls
181 spinlocks if at all possible. Its sole purpose is to determine if it
183 reason that it might not be is if an expiry of the mount is
189 mounted, it *will* fall back to REF-walk. `d_manage()` cannot make the
190 VFS remain in RCU-walk mode, but can only tell it to get out of
194 -ECHILD if there is any reason to believe it is unsafe to enter the
195 mounted filesystem, otherwise it should return 0.
198 initiated or is being considered, otherwise it returns 0.
205 much as it can expire any unused dentry information from the dcache.
209 mounting to the automount daemon, it must involve the automount daemon
223 symbolic links or empty directories any time it likes. If the unmount
225 it was before the mount or creation, so that any access of the name
234 unmounted. So it is generally safest to use the autofs expiry
239 time stamp on each directory or symlink. For symlinks it genuinely
241 out where it points to. For directories the field is used slightly
243 checks if it is found to be in use (ie. open file descriptor or
265 However, it may be used again for amd format mount maps (which are
270 When autofs considers a directory it checks the `last_used` time and
271 compares it with the "timeout" value set when the filesystem was
272 mounted, though this check is ignored in some cases. It also checks if
273 the directory or anything below it is in use. For symbolic links,
281 mounts. If it finds something in the root directory to expire it will
290 indirect mounts. If it selects an object to expire, it will notify
353 access it but it isn't there) or that it has been selected for expiry.
362 "expiring" and other accesses to it block until the message is
384 mode meaning that it stops sending notifications to the daemon.
418 **AUTOFS_IOC_EXPIRE** except that it causes notification to be
419 sent to the daemon, and it blocks until the daemon acknowledges.
427 that the daemon has requested this because it is capable of
436 It is not always possible to open the root of an autofs filesystem,
438 is restarted there is no way for it to regain control of existing
442 It requires CAP_SYS_ADMIN for access.
530 happens if a write to the notification pipe fails, or if it is
560 system users can optionally use it.
568 With bind mounts and name spaces it is possible for an autofs