CF-EXECD(8)

πŸ“¦
version 3.24.1 Β· 2 versions
, in debian trixie

πŸ’– CF-EXECD(8) πŸ’–

okay bestie, we're doing this β€” it's a page from the System Manager's Manual, and it lives in the System Administration section. Let's GO πŸ¦‹


✨ NAME ✨

cf-execd β€” the scheduling daemon for cf-agent. she's the one who keeps the calendar πŸ“…


✨ SYNOPSIS ✨

cf-execd [OPTION]...  [FILE]

✨ DESCRIPTION ✨

so cf-execd is literally the scheduling daemon for cf-agent. she runs cf-agent locally according to a schedule that's specified in policy code (the executor control body, iykyk).

after a cf-agent run finishes, cf-execd gathers up the output from cf-agent, and she can be configured to email that output to a specified address πŸ“§. she can also be configured to splay (that's randomize, bestie) the execution schedule, so you don't get a million synchronized cf-agent runs all across your network at the exact same second πŸ’€

not me forgetting the glow-up: this daemon reloads its config when the SIGHUP signal is received. periodt.

✨ OPTIONS ✨

  • --help, -h β€” print the help message 🫢
  • --debug, -d β€” enable debugging output πŸ›
  • --verbose, -v β€” output verbose info about how cf-execd is behaving (she's an open book, fr fr)
  • --dry-run, -n β€” all talk and no action mode πŸ’… makes no changes, only informs you of promises not kept
  • --version, -V β€” output the version of the software
  • --file, -f value β€” specify an alternative input file than the default. heads up: this option gets overridden by FILE if you supply it as an argument πŸ‘‘
  • --define, -D value β€” define a list of comma separated classes to be defined at the start of execution
  • --negate, -N value β€” define a list of comma separated classes to be undefined at the start of execution
  • --no-lock, -K β€” ignore locking constraints during execution (ifelapsed/expireafter) if it's "too soon" to run πŸ™ˆ
  • --inform, -I β€” print basic information about changes made to the system, i.e. promises repaired
  • --diagnostic, -x β€” activate internal diagnostics (developers only πŸ§‘β€πŸ’»)
  • --log-level, -g value β€” specify how detailed logs should be. possible values: 'error', 'warning', 'notice', 'info', 'verbose', 'debug'
  • --no-fork, -F β€” run as a foreground process (do not fork)
  • --once, -O β€” run once and then exit (this implies no-fork)
  • --no-winsrv, -W β€” do not run as a service on windows β€” use this when running from a command shell (CFEngine Nova only) πŸͺŸ
  • --ld-library-path, -L value β€” set the internal value of LD_LIBRARY_PATH for child processes
  • --color, -C value β€” enable colorized output 🌈 possible values: 'always', 'auto', 'never'. if the option is used, the default value is 'auto'
  • --timestamp, -l β€” log timestamps on each line of log output ⏰
  • --ignore-preferred-augments, - β€” ignore def_preferred.json file in favor of def.json
  • --skip-db-check, - value β€” do not run database integrity checks and repairs at startup
  • --with-runagent-socket, - value β€” specify the directory for the socket for runagent requests, or 'no' to disable the socket

✨ CFENGINE ✨

CFEngine provides automated configuration management of large-scale computer systems. a system administrator describes the desired state of a system using CFEngine policy code. the program cf-agent reads policy code and attempts to bring the current system state to the desired state described. policy code is downloaded by cf-agent from a cf-serverd daemon. and the daemon cf-execd is the one responsible for running cf-agent periodically. that's her whole job bestie, and she eats every time πŸ”₯

documentation for CFEngine is available at https://docs.cfengine.com/.


✨ PROMISE THEORY ✨

CFEngine is built on principles from promise theory, proposed by Mark Burgess in 2004. promise theory is a model of voluntary cooperation between individual, autonomous actors or agents who publish their intentions to one another in the form of promises. a promise is a declaration of intent whose purpose is to increase the recipient's certainty about a claim of past, present or future behaviour. for a promise to increase certainty, the recipient needs to trust the promiser β€” but trust can also be built on the verification that previous promises have been kept, so trust plays a symbiotic relationship with promises 🫢✨

for an introduction to promise theory, please see http://arxiv.org/abs/0810.3294/


✨ AVAILABILITY ✨

cf-execd is part of CFEngine.

binary packages may be downloaded from https://cfengine.com/download/.

the source code is available at https://github.com/cfengine/ πŸ‘‘


✨ BUGS ✨

please see the public bug-tracker at https://northerntech.atlassian.net/projects/CFE/ 🐞

GitHub pull-requests may be submitted to https://github.com/cfengine/core/.


✨ SEE ALSO ✨

cf-promises(8), cf-agent(8), cf-serverd(8), cf-execd(8), cf-monitord(8), cf-runagent(8), cf-key(8)


✨ AUTHOR ✨

Mark Burgess and Northern.tech AS πŸ’œ


and that's the whole page, bestie!! this one's from CFEngine, it's the System Administration section energy, and it's signed off with CF-EXECD(8) πŸŽ€ no cap, you're now officially fluent in cf-execd. slay πŸ’…πŸŒΈ

πŸ“¦ where this page comes from