Lines Matching refs:and

16 expire timeout and requesting expire checks. As is explained below,
24 getcwd(2) and the proc file system /proc/<pid>/cwd, no longer works
31 because autofs direct mounts and the implementation of "on demand mount
32 and expire" of nested mount trees have the file system mounted directly
37 a direct mount in disguise) and indirect.
39 Here is a master map with direct and indirect map entries:
44 and the corresponding map files:
50 and so on.
56 and so on.
58 For the above indirect map an autofs file system is mounted on /test and
64 each full path, such as /automount/dparse/g1, and using it as a mount
69 But, each entry in direct and indirect maps can have offsets (making
81 and a similarly a direct mount map entry could also be:
92 to mount and umount all of the offsets as a single unit. Not really a
94 This mechanism is used for the well known "hosts" map and we have seen
98 In version 5 we mount only as we go down the tree of offsets and
103 above and so the mount points can be covered by a mount.
108 in use and is also used to access autofs file system information held
116 To be able to restart autofs leaving existing direct, indirect and
120 existing ioctl interface and add new operations to provide this
124 the uid and gid of the last user that triggered the mount needs to be
126 autofs maps. They are recorded at mount request time and an operation
137 involves scanning /proc/mounts and since it needs to be done quite
144 using this system was attempted to evaluate its suitability and it was
157 large maps. The best way to improve this is try and get back to the
173 information and return operation results:
189 point. It is returned by the open call and is used by all calls except
192 mount point file descriptor, and when requesting the uid and gid of the
195 The fields arg1 and arg2 are used to communicate parameters and results of
198 The path field is used to pass a path where it is needed and the size field
206 kernel space and return -EINVAL if the size parameter is smaller than
209 of the compiled in user space version against the module version and a
211 the structure size then a path is assumed to be present and is checked to
212 ensure it begins with a "/" and is NULL terminated, otherwise -EINVAL is
214 AUTOFS_DEV_IOCTL_VERSION_CMD, AUTOFS_DEV_IOCTL_OPENMOUNT_CMD and
215 AUTOFS_DEV_IOCTL_CLOSEMOUNT_CMD the ioctlfd is validated and if it is
225 in autofs version 5.0.4 and later in file lib/dev-ioctl-lib.c of the
235 Get the major and minor version of the autofs4 device ioctl kernel module
237 input parameter and sets the version information in the passed in structure.
242 AUTOFS_DEV_IOCTL_PROTOVER_CMD and AUTOFS_DEV_IOCTL_PROTOSUBVER_CMD
245 Get the major and minor version of the autofs4 protocol version understood
248 and sets the requested version number in structure field arg1. These
253 AUTOFS_DEV_IOCTL_OPENMOUNT and AUTOFS_DEV_IOCTL_CLOSEMOUNT
256 Obtain and release a file descriptor for an autofs managed mount point
258 the path field set and the size field adjusted appropriately as well
266 completeness and to provide for a consistent user space implementation.
269 AUTOFS_DEV_IOCTL_READY_CMD and AUTOFS_DEV_IOCTL_FAIL_CMD
272 Return mount and expire result status from user space to the kernel.
275 call and the arg1 field set to the wait queue token number, received
278 0 and for the fail call it is set to the errno of the operation.
292 ioctlfd field set to the descriptor obtained from the open call and
303 and any remaining waits in the queue released.
321 Return the uid and gid of the last process to successfully trigger a the
325 field set to the mount point in question and the size field adjusted
328 uid and arg2 the gid.
331 re-connect to mounts that may have used the original process uid and
333 This call provides the ability to obtain this uid and gid so they may be
351 request back to the daemon and waits for completion.
359 ioctlfd field set to the descriptor obtained from the open call and
360 it returns the result in the arg1 field, 1 for busy and 0 otherwise.
370 point to check and the size field adjusted appropriately. One uses the
372 variation uses the path and optionally arg1 set to an autofs mount type.
373 The call returns 1 if this is a mount point and sets arg1 to the device
374 number of the mount and field arg2 to the relevant super block magic
384 point and and also returns the super magic of the covering mount if there
387 If a path is supplied (and the ioctlfd field is set to -1) then the path
388 is looked up and is checked to see if it is the root of a mount. If a
389 type is also given we are looking for a particular autofs mount and if