[Bro-Dev] [JIRA] (BIT-276) broctl status commands should run regardless of lock

Seth Hall (JIRA) jira at bro-tracker.atlassian.net
Sun Feb 9 21:10:37 PST 2014

     [ https://bro-tracker.atlassian.net/browse/BIT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Seth Hall updated BIT-276:

    Resolution: Rejected
        Status: Closed  (was: Open)

I'm going to close this ticket due to the impending rework coming to broctl which will invalidate this ticket.

> broctl status commands should run regardless of lock
> ----------------------------------------------------
>                 Key: BIT-276
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-276
>             Project: Bro Issue Tracker
>          Issue Type: New Feature
>          Components: BroControl
>    Affects Versions: 1.5.2
>            Reporter: solomon
>            Assignee: Robin Sommer
>            Priority: High
> broctl should allow the informational commands (top, capstats, netstats, diag, peerstatus, status, et al.) to run without interference from a concurrently locked broctl process.  If there is 'broctl cron' or 'broctl start' command runnning, say, from the system crontab, use of broctl to check on the status is often delayed or prevented.  Allowing the informational commands to run unimpeded would allow monitoring suites, such as Nagios, to more easily watch the status of the cluster.  With the frequent 'cannot get lock' errors, Nagios cannot work with bro & broctl.

This message was sent by Atlassian JIRA

More information about the bro-dev mailing list