CF-EXECD(8)
π 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 howcf-execdis 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,-fvalue β specify an alternative input file than the default. heads up: this option gets overridden byFILEif you supply it as an argument π--define,-Dvalue β define a list of comma separated classes to be defined at the start of execution--negate,-Nvalue β 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,-gvalue β 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,-Lvalue β set the internal value ofLD_LIBRARY_PATHfor child processes--color,-Cvalue β 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,-β ignoredef_preferred.jsonfile in favor ofdef.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
- debian trixie: cfengine3 3.24.1-2 Β· GPL-3.0-only
- Copyright 2024 Northern.tech AS
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms