# configuration issues **URL:** \ **Category:** Zeek\ **Created:** [January 12, 1999, 9:14am UTC](https://community.zeek.org/t/configuration-issues/46 "1999-01-12T09:14:24Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Vern](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/vern/32/630_2.png) [@Vern](https://community.zeek.org/u/Vern)\ **Post date:** [January 12, 1999, 9:14am UTC](https://community.zeek.org/t/configuration-issues/46/1 "1999-01-12T09:14:24Z")
> Apparently, the output is heavily buffered. It's the usual stdio buffering. Bro catches SIGINT, so when you kill it, it should flush those files. Is that not working, or were you looking at the files while Bro was running? Bro needs a mechanism for telling it "flush your current state". A hack for this would be some sort of signal; but I think the right way to do it is to add a general mechanism for communicating with Bro (one that lets you inject [authenticated, of course] events). This is needed anyway because Bro needs to evolve towards multiple event agents (some watching network links, some perhaps running on hosts and just watching the hosts) and that will require an event communication mechanism.     Vern ---
**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:36pm UTC](https://community.zeek.org/t/configuration-issues/46/2 "2022-05-06T15:36:06Z")