[
https://bro-tracker.atlassian.net/browse/BIT-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23921#comment-23921
]
Daniel Thayer commented on BIT-1510:
------------------------------------
OK, but just to be clear, the case that you mention (when bro just takes too
long
to shut down and has to be killed with SIGKILL) is already not being handled as
a "crash".
> Crash reports when no crash happened
> ------------------------------------
>
> Key: BIT-1510
> URL: https://bro-tracker.atlassian.net/browse/BIT-1510
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: BroControl
> Affects Versions: git/master
> Reporter: Seth Hall
> Fix For: 2.5
>
>
> We need to make broctl stop sending crash reports when Bro was shutdown by a
> signal. It's confusing for users because they will get these emails
> sporadically when restarting Bro.
> The crash report typically has the following text and no backtrace:
> ==== stderr.log
> KILLED
> received termination signal
--
This message was sent by Atlassian JIRA
(v7.1.0-OD-05-006#71001)
_______________________________________________
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
