| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001436 | ClearOS | app-base - Base System | public | 2013-11-21 10:33 | 2015-02-05 12:21 |
|
| Reporter | user2 | |
| Assigned To | user2 | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | 6.6.0 Beta 2 | Fixed in Version | 6.6.0 Beta 2 | |
|
| Summary | 0001436: 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.
|
| Additional Information | For ClearOS 6, add a workaround for the web proxy. |
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships