0001701: Ulimits defined in /etc/security/limits.conf (or limits.d) are not effective on boot

ClearFoundation Tracker - ClearOS

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0001701

ClearOS

system-base - Base System

public

2014-05-14 10:06

2015-02-05 10:37

Reporter

user2

Assigned To

user2

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

no change required

Platform

OS Version

Product Version

Target Version

7.0.0 Alpha 2

Fixed in Version

7.0.0 Alpha 2

Summary

0001701: Ulimits defined in /etc/security/limits.conf (or limits.d) are not effective on boot

Description

The /etc/security/limits.d/95-clearos.conf file in the ClearOS base package sets the number of file descriptors to 16384 (default is 1024) and number of processes to 4096 (default is 1024). These limits work when a daemon is restarted, but the old defaults are still used on boot. Wah!? This little gem confirms the behavior -- original @ http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Fc_special_considerations_linux.html [^]

   Important: If you use a system startup script such as /etc/init.d/was
   or /etc/rc.*/SXXWebSphere to start WebSphere Application Server at
   system boot up time, init.d invokes the startup scripts with the maximum
   number of file descriptors set to 1024 instead of the system default value
   that is set in /etc/security/limits.conf (65536). To avoid this problem, after
   a system boot up, manually run /etc/init.d/was restart from a root shell.
   This will ensure that WebSphere Application Server is restarted with the
   correct file descriptor limit.

Well... that's certainly unexpected behavior.

Steps To Reproduce

Additional Information