[Bro-Dev] #292: Cluttering of alarm.log with serialization messages

[Bro Tracker]

#292: Cluttering of alarm.log with serialization messages
-------------------------+--------------------------------------------------
  Reporter:  vallenti    |       Owner:  robin 
      Type:  Problem     |      Status:  new   
  Priority:  Normal      |   Milestone:  Bro1.6
 Component:  BroControl  |     Version:  1.5.1 
Resolution:              |    Keywords:        
-------------------------+--------------------------------------------------
Changes (by seth):

  * milestone:  => Bro1.6


Comment:

 I just checked the code and it looks pretty straight forward to move this
 to another file.  Any ideas for a file name to use for this type of
 logging message?  Since the normal output is to stderr if the alarm log
 isn't open, maybe it makes sense to name the log file stderr.log?

 I can do development on this, it should just take a few minutes and I'd
 also like to have a different way to handle these messages.

-- 
Ticket URL: <http://tracker.icir.org/bro/ticket/292#comment:2>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker