5 commits

Author	SHA1	Message	Date
Josh Soref	21e0d777b3	Spelling fixes: scripts ... * accessing * across * adding * additional * addresses * afterwards * analyzer * ancillary * answer * associated * attempts * because * belonging * buffer * cleanup * committed * connects * database * destination * destroy * distinguished * encoded * entries * entry * hopefully * image * include * incorrect * information * initial * initiate * interval * into * java * negotiation * nodes * nonexistent * ntlm * occasional * omitted * otherwise * ourselves * paragraphs * particular * perform * received * receiver * referring * release * repetitions * request * responded * retrieval * running * search * separate * separator * should * synchronization * target * that * the * threshold * timeout * transaction * transferred * transmission * triggered * vetoes * virtual Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>	2022-11-02 17:36:39 -04:00
Christian Kreibich	14188fc7a7	Add Supervisor::node_status notification event ... The Supervisor generates this event every time it receives a status update from the stem, meaning a node got created or re-created. A corresponding SupervisorControl::node_status event relays the same information for users interacting with the Supervisor over Broker.	2022-05-30 21:36:35 -07:00
Christian Kreibich	efaa9ec3be	Add support for making the supervisor listen for requests ... The supervisor now starts listening on the configured Broker default address and port when the new boolean SupervisorControl::enable_listen is T. Listening remains disabled by default. Listening allows nodes to communicate with the supervisor via the events laid out in control.zeek, to conduct further node management.	2021-07-08 13:12:53 -07:00
Jon Siwek	fdfd729206	Add note that Supervisor script APIs are unstable until 4.0	2020-01-27 13:51:01 -08:00
Jon Siwek	bbdf5f8938	Move supervisor control events into SupervisorControl namespace	2020-01-22 13:28:20 -08:00