Christian Kreibich 93ea03a081 Management framework: place each Zeek process in its own working dir ... This establishes a directory "nodes" in Management::state_dir and places each Zeek process into a subdirectory in it, named after the Zeek process. For example, node "worker-01" runs with cwd <state_dir>/nodes/worker-01/. Explicitly configured directories can override the naming logic, and also ignore the state directory if they're absolute paths. One exception remains: the Supervisor itself -- we'd have to use LogAscii::logdir to automatically place it too in its own directory, but that feature currently does not interoperate with log rotation.		2022-05-26 12:56:02 -07:00
..
agent	Management framework: place each Zeek process in its own working dir	2022-05-26 12:56:02 -07:00
controller	Management framework: place each Zeek process in its own working dir	2022-05-26 12:56:02 -07:00
node	Management framework: set defaults for log rotation and persistent state	2022-05-26 12:55:10 -07:00
__load__.zeek	Management framework: set defaults for log rotation and persistent state	2022-05-26 12:55:10 -07:00
config.zeek	Management framework: add spool and state directory config settings	2022-05-25 13:56:23 -07:00
log.zeek	Management framework: move role variable from logging into framework-wide config	2022-05-25 13:56:23 -07:00
persistence.zeek	Management framework: set defaults for log rotation and persistent state	2022-05-26 12:55:10 -07:00
request.zeek	Reorg of the cluster controller to new "Management framework" layout	2022-02-09 18:09:42 -08:00
types.zeek	Management framework: comment and layouting tweaks, no functional change	2022-05-25 13:56:23 -07:00
util.zeek	Reorg of the cluster controller to new "Management framework" layout	2022-02-09 18:09:42 -08:00