CGRULESENGD(8)

πŸ“¦
version 3.2.0 Β· 2 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– CGRULESENGD πŸ’–

the control group rules daemon β€” from the libcgroup Manual, bestie. yes we're doing this. it's giving sysadmin but make it cute πŸŽ€


✨ NAME ✨

cgrulesengd β€” control group rules daemon


🌸 SYNOPSIS 🌸

cgrulesengd [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so. cgrulesengd is a daemon, and its whole job β€” its entire main character arc β€” is distributing processes to control groups. that's it. that's the vibe. πŸ’…

the way it works: whenever any process changes its effective UID or GID, cgrulesengd goes and inspects the list of rules it loaded from the cgrules.conf file and the files in the cgrules.d directory (peep cgrules.d(5) for potential conflicts, iykyk πŸ‘€) and then moves that process to the appropriate control group. slay.

the list of rules gets read during the daemon startup and cached in the daemon's memory. no cap. and when it receives the SIGUSR2 signal, the daemon reloads the list of rules. when it receives the SIGUSR1 signal, the daemon reloads the list of templates. two different signals, two different reloads, don't mix them up fr fr 😭

also it opens a standard unix socket to receive 'sticky' requests from cgexec. iconic behavior honestly.


✨ OPTIONS ✨

  • -h|--help β€” display help. that's it, that's the option. 🫢
  • -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 destinations. πŸ’–
  • -n|--nodaemon β€” don't fork the daemon, stay in the foreground. like, just hang out here with us. πŸ₯Ί
  • -v|--verbose β€” display more log messages. this option can be used three times to enable more verbose log messages. more v's = more words. πŸ“’
  • -q|--quiet β€” display less log messages. shhhh. 🀫
  • -Q|--nolog β€” disable logging. completely. gone. πŸ’€
  • -d|--debug β€” equivalent to '-nvvvf -', i.e. don't fork the daemon, display all log messages and write them to the standard output. the everything-bagel of options, periodt. πŸ”₯
  • -u <user>|--socket-user=<user> β€” 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. πŸ‘‘
  • -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. that's the whole menu, bestie, pick your fighter. ⭐

πŸŽ€ FILES πŸŽ€

  • /etc/cgrules.conf β€” default libcgroup configuration file
  • /etc/cgrules.d β€” default libcgroup configuration files directory
  • /etc/cgconfig.conf β€” default templates file
  • /etc/cgconfig.d β€” default templates directory

πŸ’œ SEE ALSO πŸ’œ

cgrules.conf(5), cgrules.d(5)


mwah πŸ’‹ this page came from the libcgroup Manual, Linux, dated 2009-02-18 β€” a whole vintage icon, honestly. go forth and sort your processes, bestie. πŸ§šπŸ’–

πŸ“¦ where this page comes from