Re: [Bro-Dev] input framework and tuning options

On Mon, Jan 22, 2018 at 11:31 PM, Scott Campbell wrote: > The data source is a log file that grows at ~7-9k records/sec and > consists of small text lines of < 512 bytes, newline delimited. > > The primary symptom here is a steadily growing memory footprint even > though the

Re: [Bro-Dev] Misleading error message

On Mon, Jan 29, 2018 at 3:15 PM, Jim Mellander wrote: > Wouldn't it be more reasonable to check at the end of each > script when loaded that there are no dangling functions, expressions, etc. > Yes, it's definitely reasonable to want a better error message here and I

[Bro-Dev] Misleading error message

Hi all: I was tinkering with the sumstats code, and inadvertantly deleted the final "}" closing out the last function. When running the code, the misleading error message is received: error in /Users/melland/traces/bro/share/bro/base/frameworks/tunnels/./main.bro, line 8: syntax error, at or

Re: [Bro-Dev] 'async' update and proposal

On Mon, Jan 29, 2018 at 11:00 AM, Robin Sommer wrote: > as you point out, that wouldn't solve inter-event dependencies. > Per Jan's mail, one can work around that with custom code The inter-event dependencies + code understandability/readability issue that Johanna points out is

Re: [Bro-Dev] 'async' update and proposal

Jan wrote: > First of all, this async keyword reminds me of asynchronous programming > in C#: Nice, didn't know that. > For the C# async paradigm, people say that async is like a zombie > plague as a single asynchronous function can start "infecting" your > code base by propagating async