Lines Matching refs:daemon
36 as the "automount daemon" or simply "the daemon".
40 can each be managed separately, or all managed by the same daemon.
49 Objects can only be created by the automount daemon: symlinks are
100 automount daemon asking it to find and mount the filesystem. The
101 autofs `d_automount` method then waits for the daemon to report that
110 automount daemon would not be able to mount a filesystem on the 'trap'
138 lookup is the automount daemon and that the mount has been
140 discussed later. This allows the automount daemon not to get
145 be managed by the same daemon. For the daemon to be able to mount
148 the automount daemon. It must only return it when a mount has
160 - -ENOENT if the automount daemon failed to mount anything,
164 - or any other error sent down by the automount daemon.
209 mounting to the automount daemon, it must involve the automount daemon
221 With version 4 of the protocol, the automount daemon can try to
237 Normally the daemon only wants to remove entries which haven't been
254 The daemon is able to ask autofs if anything is due to be expired,
283 automount daemon needs to unmount any filesystems mounted below the
291 the daemon using the notification mechanism described below. This
292 will block until the daemon acknowledges the expiry notification.
297 `d_manage` will block until the daemon affirms that the unmount has
301 Communicating with autofs: detecting the daemon
304 There are several forms of communication between the automount daemon
305 and the filesystem. As we have already seen, the daemon can create and
307 autofs knows whether a process requesting some operation is the daemon
313 process in that process group is considered to come from the daemon.
314 If the daemon ever has to be stopped and restarted a new pgid can be
322 notification messages to this pipe for the daemon to respond to.
371 capability, or must be the automount daemon.
384 mode meaning that it stops sending notifications to the daemon.
419 sent to the daemon, and it blocks until the daemon acknowledges.
427 that the daemon has requested this because it is capable of
437 particularly a *direct* mounted filesystem. If the automount daemon
498 in `setpipefd.pipefd` to re-establish communication with a daemon.
500 daemon.
538 be treated in the same way as if they came from the daemon, so mount
575 The automount daemon is only able to manage a single mount location for