# Version: 2.0-907 -- Bro manager memory exhaustion

**URL:** <https://community.zeek.org/t/version-2-0-907-bro-manager-memory-exhaustion/2387>\
**Category:** Zeek\
**Created:** [August 1, 2012, 9:33pm UTC](https://community.zeek.org/t/version-2-0-907-bro-manager-memory-exhaustion/2387 "2012-08-01T21:33:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Scott\_Campbell](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@Scott\_Campbell](https://community.zeek.org/u/Scott_Campbell)\
**Post date:** [August 1, 2012, 9:33pm UTC](https://community.zeek.org/t/version-2-0-907-bro-manager-memory-exhaustion/2387/1 "2012-08-01T21:33:24Z")

</div>

This is not a particularly well thought out venture, but the intention  
is to lower the pain associated with the process through example.  
With this new functionality, bro itself is is well placed for  
clustering, but the systems side - like OS tuning, driver  
configuration, traffic distribution etc etc still could be much better  
documented.

I completely agree that use cases are probably the best way to go  
about conveying this information. See you there -

cheers,  
scott

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:40pm UTC](https://community.zeek.org/t/version-2-0-907-bro-manager-memory-exhaustion/2387/2 "2022-05-06T15:40:28Z")

</div>