[
https://issues.apache.org/jira/browse/DAEMON-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983056#action_12983056
]
Roberto Resoli commented on DAEMON-192:
---------------------------------------
I agree. In the meantime, I found that setting limits it's only matter to run
ulimit ( in order to set max number of open files, for example: "ulimit -n <max
number of open files>" ) just before of launching jsvc.
The limits are retained even when jsvc running user is downgraded.
> Make jsvc enforce /etc/security/limits.conf , or add a parameter for setting
> limits
> -----------------------------------------------------------------------------------
>
> Key: DAEMON-192
> URL: https://issues.apache.org/jira/browse/DAEMON-192
> Project: Commons Daemon
> Issue Type: Improvement
> Components: Jsvc
> Environment: Linux, maybe all Unixes
> Reporter: Roberto Resoli
> Priority: Minor
>
> When launched with -user parameter, jsvc downgrades user via setuid() system
> call, but the operating system limits (max number of open files, for example)
> remains the same.
> This is not convenient for running daemons (like Tomcat) which very often
> need a customization of such limits.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
