commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DAEMON-192) Make jsvc enforce /etc/security/limits.conf , or add a parameter for setting limits
Date Mon, 06 Jun 2011 14:46:59 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mladen Turk resolved DAEMON-192.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.6

Resolving by updated Tomcat7.sh in samples directory.
It has an example of how to set the maximum fd's before
running the daemon.
One can use and customize a give recipe.

> 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
>             Fix For: 1.0.6
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message