Arne Welzel 60d8872969 Known: Keep &create_expire on local tables/sets valid ... After switching the known scripts away from broker stores, the &create_expire value of the local tables/sets of the known scripts wasn't in effect due to Cluster::node_up() and Cluster::node_down() re-assigning these without keeping the &create_expire attribute intact. This broke the "log hosts every 24h" behavior. Closes #3540		2024-01-10 09:07:43 +01:00
..
community-id-logging.zeek	policy/community-id: Do not use new_connection()	2023-05-10 17:48:33 +02:00
known-hosts.zeek	Known: Keep &create_expire on local tables/sets valid	2024-01-10 09:07:43 +01:00
known-services.zeek	Known: Keep &create_expire on local tables/sets valid	2024-01-10 09:07:43 +01:00
mac-logging.zeek	Rename all scripts to have ".zeek" file extension	2019-04-11 21:12:40 -05:00
speculative-service.zeek	GH-1119: add base/protcols/conn/removal-hooks.zeek	2020-09-11 12:12:10 -07:00
vlan-logging.zeek	Rename all scripts to have ".zeek" file extension	2019-04-11 21:12:40 -05:00
weirds.zeek	Remove concept of multiple timer managers	2020-01-31 10:13:09 -07:00