cgrulesengd(8) [centos man page]
CGRULESENGD(8) libcgroup Manual CGRULESENGD(8) NAME
cgrulesengd - control group rules daemon SYNOPSIS
cgrulesengd [options] DESCRIPTION
cgrulesengd is a daemon, which distributes processes to control groups. When any process changes its effective UID or GID, cgrulesengd inspects the list of rules loaded from the cgrules.conf file and moves the process to the appropriate control group. The list of rules is read during the daemon startup is are cached in the daemon's memory. The daemon reloads the list of rules when it receives SIGUSR2 signal. The daemon reloads the list of templates when it receives SIGUSR1 signal. The daemon opens a standard unix socket to receive 'sticky' requests from cgexec. OPTIONS
-h|--help Display help. -f <path>|--logfile=<path> Write log messages to the given log file. When '-' is used as <path>, log messages are written to the standard output. If '-f' and '-s' are used together, the logs are sent to both destinations. -s[facility]|--syslog=[facility] Write log messages to syslog. The default facility is DAEMON. If '-f' and '-s' are used together, the logs are sent to both destina- tions. -n|--nodaemon Don't fork the daemon, stay in the foreground. -v|--verbose Display more log messages. This option can be used three times to enable more verbose log messages. -q|--quiet Display less log messages. -Q|--nolog Disable logging. -d|--debug Equivalent to '-nvvvf -', i.e. don't fork the daemon, display all log messages and write them to the standard output. -u <user>|--socket-user=<user> -g <group>|--socket-group=<group> Set the owner of cgrulesengd socket. Assumes that cgexec runs with proper suid permissions so it can write to the socket when cgexec --sticky is used. ENVIRONMENT VARIABLES
CGROUP_LOGLEVEL controls verbosity of the tool. Allowed values are DEBUG, INFO, WARNING or ERROR. FILES
/etc/cgrules.conf the default libcgroup configuration file SEE ALSO
cgrules.conf (5) Linux 2009-02-18 CGRULESENGD(8)
Check Out this Related Man Page
LVMETAD(8) System Manager's Manual LVMETAD(8) NAME
lvmetad - LVM metadata cache daemon SYNOPSIS
lvmetad [-l {all|wire|debug}] [-p pidfile_path] [-s socket_path] [-f] [-h] [-V] [-?] DESCRIPTION
lvmetad is a metadata caching daemon for LVM. The daemon receives notifications from udev rules (which must be installed for LVM to work correctly when lvmetad is in use). Through these notifications, lvmetad has an up-to-date and consistent image of the volume groups avail- able in the system. By default, lvmetad, even if running, is not used by LVM. See lvm.conf(5). OPTIONS
To run the daemon in a test environment both the pidfile_path and the socket_path should be changed from the defaults. -f Don't fork, but run in the foreground. -h, -? Show help information. -l {all|wire|debug} Select the type of log messages to generate. Messages are logged by syslog. Additionally, when -f is given they are also sent to standard error. Since release 2.02.98, there are two classes of messages: wire and debug. Selecting 'all' supplies both and is equivalent to a comma-separated list -l wire,debug. Prior to release 2.02.98, repeating -d from 1 to 3 times, viz. -d, -dd, -ddd, increased the detail of messages. -p pidfile_path Path to the pidfile. This overrides both the built-in default (#DEFAULT_PID_DIR#/lvmetad.pid) and the environment variable LVM_LVMETAD_PIDFILE. This file is used to prevent more than one instance of the daemon running simultaneously. -s socket_path Path to the socket file. This overrides both the built-in default (/run/lvm/lvmetad.socket) and the environment variable LVM_LVMETAD_SOCKET. To communicate successfully with lvmetad, all LVM2 processes should use the same socket path. -V Display the version of lvmetad daemon. ENVIRONMENT VARIABLES
LVM_LVMETAD_PIDFILE Path for the pid file. LVM_LVMETAD_SOCKET Path for the socket file. SEE ALSO
lvm(8), lvm.conf(5) Red Hat Inc LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) LVMETAD(8)