[Bro-Dev] [JIRA] (BIT-178) BroControl's check process should check for ability to set "ulimit -d"

Adam Slagell (JIRA) jira at bro-tracker.atlassian.net
Sun Jan 10 08:38:00 PST 2016


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

Adam Slagell updated BIT-178:
-----------------------------
    Issue Type: Problem  (was: New Feature)

> BroControl's check process should check for ability to set "ulimit -d"
> ----------------------------------------------------------------------
>
>                 Key: BIT-178
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-178
>             Project: Bro Issue Tracker
>          Issue Type: Problem
>          Components: BroControl
>    Affects Versions: 1.5.2
>            Reporter: Seth Hall
>            Assignee: Daniel Thayer
>            Priority: Low
>              Labels: warning
>             Fix For: 2.5
>
>
> If the bro process(es) are run as a non-root user, the "ulimit \-d" call done during the run-bro script will fail (on freebsd at least) and cause obtuse failures when the Bro processes grow beyond the default 512M data segment size (on freebsd again).  The check process could verify that setting can be set and possibly give recommendations for linux and freebsd on how to increase that setting globally.
> For documentation purposes, to set it globally to the value set by the run-bro script put the following in the /boot/loader.conf file and reboot:
> {noformat}
> kern.maxdsiz=1610612736
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.1.0-OD-03-049#71001)


More information about the bro-dev mailing list