Lines Matching full:an

17 are things such as setting an autofs mount catatonic, setting the
19 certain types of autofs triggered mounts can end up covering an autofs
38 module source you will see a third type called an offset, which is just
60 For the above indirect map an autofs file system is mounted on /test and
65 The way that direct mounts are handled is by making an autofs mount on
74 For example, an indirect mount map entry could also be::
92 One of the issues with version 4 of autofs was that, when mounting an
107 The current autofs implementation uses an ioctl file descriptor opened
121 implement an isolated operation it was decided to re-implement the
128 autofs maps. They are recorded at mount request time and an operation
136 ENOENT so the re-implementation allows user space to send an actual
141 in the mount table. An operation to lookup the mount status of a mount
145 ioctl mechanism in favor of systems such as Netlink. An implementation
149 complexity. There's no question that the Generic Netlink system is an
152 message bus implementation rather than specifically an ioctl replacement.
160 way the expire was done long ago. That is, when an expire request is
202 The ioctlfd field is a mount point file descriptor of an autofs mount
230 not a valid descriptor or doesn't correspond to an autofs mount point
231 an error of -EBADF, -ENOTTY or -EINVAL (not an autofs descriptor) is
238 An example of an implementation which uses this interface can be seen
250 implementation. It requires an initialized struct autofs_dev_ioctl as an
260 by loaded module. This call requires an initialized struct autofs_dev_ioctl
270 Obtain and release a file descriptor for an autofs managed mount point
271 path. The open call requires an initialized struct autofs_dev_ioctl with
275 shown in /proc/mounts. The close call requires an initialized struct
287 Both of these calls require an initialized struct autofs_dev_ioctl
299 Normally this is set at mount time using an option but when reconnecting
305 The call requires an initialized struct autofs_dev_ioctl with the
320 The call requires an initialized struct autofs_dev_ioctl with the
327 Set the expire timeout for mounts within an autofs mount point.
329 The call requires an initialized struct autofs_dev_ioctl with the
339 The call requires an initialized struct autofs_dev_ioctl with the path
344 When reconstructing an autofs mount tree with active mounts we need to
354 Issue an expire request to the kernel for an autofs mount. Typically
357 The call requires an initialized struct autofs_dev_ioctl with the
359 addition an immediate expire that's independent of the mount timeout,
367 to the given ioctlfd for mounts that can be expired, issues an expire
373 Checks if an autofs mount point is in use.
375 The call requires an initialized struct autofs_dev_ioctl with the
386 The call requires an initialized struct autofs_dev_ioctl. There are two
391 set to an autofs mount type. The call returns 1 if this is a mount point