On 11/1/18 7:43 AM, Robin Sommer wrote:
> The oberservations / thoughts in this thread seem worth a ticket I'd
> say. We can refine this over time if the current semantics aren't
> quite ideal yet.
Okay Robin, I've created https://github.com/bro/bro/issues/201 for this.
Thanks,
-C.
The oberservations / thoughts in this thread seem worth a ticket I'd
say. We can refine this over time if the current semantics aren't
quite ideal yet.
Robin
On Tue, Oct 30, 2018 at 13:17 -0700, Christian Kreibich wrote:
> Hi folks,
>
> I would agree that it takes a bit of experimentation to
Hi folks,
I would agree that it takes a bit of experimentation to figure out
exactly when a change handler fires and how to reliably initialize or
update things based on an option's value.
Consider this:
module Foo;
export { option foo = F; }
function foo_handler(ID: string,
-Dev] Config Framework Feedback
Message received from outside the Battelle network. Carefully examine it before
you open any links or attachments.
> On Oct 30, 2018, at 2:09 PM, Hosom, Stephen M wrote:
>
> I bumped into a limitation that was a little frustrating to work around with
>
> On Oct 30, 2018, at 2:09 PM, Hosom, Stephen M wrote:
>
> I bumped into a limitation that was a little frustrating to work around with
> the config framework.
>
>
> It is inconvenient that values stored in files read by adding to
> Config::config_files are not available within the bro_init
I bumped into a limitation that was a little frustrating to work around with
the config framework.
It is inconvenient that values stored in files read by adding to
Config::config_files are not available within the bro_init event. After
reviewing how the Config framework works, I understand
