Lines Matching refs:daemon

40 CacheFiles uses a userspace daemon to do some of the cache management - such as
50 to communication with the daemon.  Only one thing may have this open at once,
51 and while it is open, a cache is at least partially in existence.  The daemon
68 The use of CacheFiles and its daemon requires the following features to be
124 The cache is started by running the daemon.  The daemon opens the cache device,
128 The daemon is run as follows::
153 mountpoints, but the daemon can't avoid them.
205 The userspace daemon scans the cache to build up a table of cullable objects.
222 to the graveyard from which the daemon will actually delete them.
224 The daemon uses dnotify to monitor the graveyard directory, and will delete
320      (presumed to be the cachefilesd daemon), which by default will be::
325      daemon's label.  By default, this will be::
329      SELinux transitions the daemon's security ID to the module's security ID
332 	type_transition <daemon's-ID> kernel_t : process <module's-ID>;
344 The daemon's security ID gives it only a very restricted set of permissions: it
403 cache management daemon (cachefilesd).
499 the data and writing it into the cache is delegated to a user daemon.
508 and user daemon. The protocol can be modeled as::
510 	kernel --[request]--> user daemon --[reply]--> kernel
512 CacheFiles will send requests to the user daemon when needed.  The user daemon
517 The user daemon then reads the devnode to fetch a request to process.  It should
519 the request, the user daemon should write the reply to the devnode.
563 daemon.  The payload format is of the form::
584 	  which the user daemon can perform write/llseek file operations on the
588 The user daemon can use the given (volume_key, cookie_key) pair to distinguish
589 the requested cache file.  With the given anonymous fd, the user daemon can
594 anonymous fds.  The user daemon may duplicate anonymous fds from the initial
596 be mapped to multiple anonymous fds, while the usr daemon itself needs to
599 When implementing a user daemon, please be careful of RLIMIT_NOFILE,
604 The user daemon should reply the OPEN request by issuing a "copen" (complete
615 	  user daemon.
622 sent to the user daemon.  This tells the user daemon to close all anonymous fds
631 READ request (opcode CACHEFILES_OP_READ) to the user daemon. This tells the user
632 daemon to fetch the contents of the requested file range.  The payload is of the
647 When it receives a READ request, the user daemon should fetch the requested data
650 When it has finished processing the READ request, the user daemon should reply