Lines Matching refs:daemon

37 CacheFiles uses a userspace daemon to do some of the cache management - such as
47 to communication with the daemon.  Only one thing may have this open at once,
48 and whilst it is open, a cache is at least partially in existence.  The daemon
65 The use of CacheFiles and its daemon requires the following features to be
130 The cache is started by running the daemon.  The daemon opens the cache device,
134 The daemon is run as follows:
164 mountpoints, but the daemon can't avoid them.
223 The userspace daemon scans the cache to build up a table of cullable objects.
242 to the graveyard from which the daemon will actually delete them.
244 The daemon uses dnotify to monitor the graveyard directory, and will delete
339      (presumed to be the cachefilesd daemon), which by default will be:
344      daemon's label.  By default, this will be:
348      SELinux transitions the daemon's security ID to the module's security ID
351 	type_transition <daemon's-ID> kernel_t : process <module's-ID>;
363 The daemon's security ID gives it only a very restricted set of permissions: it
423 cache management daemon (cachefilesd).