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
..
control	Remove trailing whitespace from script files	2021-10-20 09:57:09 -07:00
dpd	Add analyzer_confirmation and analyzer_violation events	2021-11-23 19:36:50 -07:00
files	update uses of "when" in base scripts to include captures	2022-01-07 14:53:33 -08:00
intel	Fix host header normalization in intel framework.	2021-12-21 21:54:47 +01:00
management	Management framework: place each Zeek process in its own working dir	2022-05-26 12:56:02 -07:00
netcontrol	Support for log filter policy hooks	2020-09-30 12:32:45 -07:00
notice	update uses of "when" in base scripts to include captures	2022-01-07 14:53:33 -08:00
packet-filter	More bro-to-zeek renaming in scripts and other files	2019-05-16 02:36:41 -05:00
signatures	Hopefully the last major script reorganization.	2011-08-05 23:09:53 -04:00
software	update uses of "when" in base scripts to include captures	2022-01-07 14:53:33 -08:00