mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
92565d4739
util::safe_write() calls abort() in case of EAGAIN errors. This is easily observed when starting clusters with 32 workers or more. Add a custom write_message() function handling EAGAIN by retrying after a small sleep. It's not clear a more complicated poll() would be much better: The pipe might be ready for writing, but then our message might not actually fit in, resulting in another EAGAIN error. And even poll() would introduce blocking/sleeping code. Take some precautions against the stem and the supervisor dead-locking when both pipes are full by draining the other end on EAGAIN errors. Closes #3043 |
||
|---|---|---|
| .. | ||
| config-bare-mode.zeek | ||
| config-cluster-leftover-log-archival.zeek | ||
| config-cluster-log-archival.zeek | ||
| config-cluster-multi-logger.zeek | ||
| config-cluster-pcap.zeek | ||
| config-cluster.zeek | ||
| config-directory.zeek | ||
| config-env.zeek | ||
| config-output-redirect.zeek | ||
| config-scripts.zeek | ||
| create-interface-pcap-file-error.zeek | ||
| create.zeek | ||
| destroy.zeek | ||
| large-cluster.zeek | ||
| node_status.zeek | ||
| output-redirect-hook.zeek | ||
| output-redirect.zeek | ||
| restart.zeek | ||
| revive-leaf.zeek | ||
| revive-stem.zeek | ||
| status.zeek | ||