Re: [Bro-Dev] Broker has landed in master, please test

> On Jun 1, 2018, at 11:37 AM, Azoff, Justin S wrote: > > I could never figure out what was causing the problem, and it's possible that > not doing anything anymore is why it's better now. I'm mostly > using for syncing input files across all the workers and one of > them does have 300k

Re: [Bro-Dev] Broker has landed in master, please test

On Wed, May 23, 2018 at 20:16 +, Adam wrote: > I think those question belong on the main list which is for using Bro > and its language. This list is really more about development of Bro > itself. Just to give context here, the reason I sent the original mail about Broker here, including

Re: [Bro-Dev] Broker has landed in master, please test

On 5/23/18 3:12 PM, Michael Dopheide wrote: > For here though, can you elaborate on the going down to one proxy?  My > understanding still isn't strong, but that seems to be opposed to the > idea of using Cluster::publish_hrw to spread memory across proxies. The idea is to try starting with

Re: [Bro-Dev] Broker has landed in master, please test

On May 23, 2018, at 3:12 PM, Michael Dopheide > wrote: Do you want dumb programming questions asked here or on the main Bro list? While most people might not need it yet, discussion there might help get more people interested or help avoid issues with

Re: [Bro-Dev] Broker has landed in master, please test

Do you want dumb programming questions asked here or on the main Bro list? While most people might not need it yet, discussion there might help get more people interested or help avoid issues with custom policy conversion. For here though, can you elaborate on the going down to one proxy? My

[Bro-Dev] Broker has landed in master, please test

We merged the new Broker version into Bro master yesterday. As this a major change to one of Bro's core components, I wanted to send a quick heads-up here, along with a couple of notes. With this merge we are completely replacing usage of Bro's classic communication system with Broker. All the