mirror of
https://github.com/zeek/zeek.git
synced 2025-10-06 00:28:21 +00:00
38e1dc9ca4
Once a BasicThread leaves its run() method, a thread is now marked for cleaning up, and the ThreadMgr will soon join it to release the OS resources. Also, adding a function Log::remove_stream() that remove a logging stream, stopping all writer threads that are associated with it. Note, however, that removing a *filter* from a stream still doesn't clean up any threads. The problem is that because of the output paths potentially being created dynamically it's unclear if the writer thread will still be needed in the future. We could add clean writers up with timeouts, but that doesn't sound great either. So for now, the only way to sure clean up logging threads is to remove the entire stream. Also note that cleanup doesn't work with input threads yet, which don't seem to terminate (at least in the case I tried). |
||
|---|---|---|
| .. | ||
| cluster | ||
| communication | ||
| control | ||
| dpd | ||
| input | ||
| intel | ||
| logging | ||
| metrics | ||
| notice | ||
| packet-filter | ||
| reporter | ||
| signatures | ||
| software | ||
| tunnels | ||