[asterisk-bugs] [JIRA] (ASTERISK-26077) safe_asterisk ulimit can be above kernel max

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230852#comment-230852 ] 

Asterisk Team commented on ASTERISK-26077:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> safe_asterisk ulimit can be above kernel max
> --------------------------------------------
>
>                 Key: ASTERISK-26077
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26077
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Contrib/General
>            Reporter: rsw686
>            Severity: Critical
>
> safe_asterisk calculates the ulimit based on file-max divided by two. On certain systems this value can be above the kernel max, which results in the open file limit not being applied. Some research shows the kernel max is 1024 * 1024 and I am able to successfully execute ulimit -n 1048576.
> cat /proc/sys/fs/file-max
> 2466684
> 2466684 / 2 = 1233342
> ulimit -n 1233342
> -bash: ulimit: open files: cannot modify limit: Operation not permitted



--
This message was sent by Atlassian JIRA
(v6.2#6252)