Lines Matching full:an
15 are things such as setting an autofs mount catatonic, setting the
17 certain types of autofs triggered mounts can end up covering an autofs
36 module source you will see a third type called an offset, which is just
58 For the above indirect map an autofs file system is mounted on /test and
63 The way that direct mounts are handled is by making an autofs mount on
72 For example, an indirect mount map entry could also be:
90 One of the issues with version 4 of autofs was that, when mounting an
105 The current autofs implementation uses an ioctl file descriptor opened
119 implement an isolated operation it was decided to re-implement the
126 autofs maps. They are recorded at mount request time and an operation
134 ENOENT so the re-implementation allows user space to send an actual
139 in the mount table. An operation to lookup the mount status of a mount
143 ioctl mechanism in favor of systems such as Netlink. An implementation
147 complexity. There's no question that the Generic Netlink system is an
150 message bus implementation rather than specifically an ioctl replacement.
158 way the expire was done long ago. That is, when an expire request is
200 The ioctlfd field is a mount point file descriptor of an autofs mount
228 not a valid descriptor or doesn't correspond to an autofs mount point
229 an error of -EBADF, -ENOTTY or -EINVAL (not an autofs descriptor) is
236 An example of an implementation which uses this interface can be seen
248 implementation. It requires an initialized struct autofs_dev_ioctl as an
258 by loaded module. This call requires an initialized struct autofs_dev_ioctl
268 Obtain and release a file descriptor for an autofs managed mount point
269 path. The open call requires an initialized struct autofs_dev_ioctl with
273 shown in /proc/mounts. The close call requires an initialized struct
285 Both of these calls require an initialized struct autofs_dev_ioctl
297 Normally this is set at mount time using an option but when reconnecting
303 The call requires an initialized struct autofs_dev_ioctl with the
318 The call requires an initialized struct autofs_dev_ioctl with the
325 Set the expire timeout for mounts within an autofs mount point.
327 The call requires an initialized struct autofs_dev_ioctl with the
337 The call requires an initialized struct autofs_dev_ioctl with the path
342 When reconstructing an autofs mount tree with active mounts we need to
352 Issue an expire request to the kernel for an autofs mount. Typically
355 The call requires an initialized struct autofs_dev_ioctl with the
357 addition an immediate expire that's independent of the mount timeout,
365 to the given ioctlfd for mounts that can be expired, issues an expire
371 Checks if an autofs mount point is in use.
373 The call requires an initialized struct autofs_dev_ioctl with the
384 The call requires an initialized struct autofs_dev_ioctl. There are two
389 set to an autofs mount type. The call returns 1 if this is a mount point