If you search the ADSM-L archives, you will see we went through this a while ago. The startup script (for us tsminst1_dsmserv.rc) contains ulimit statements that sets them to much higher values - *ulimit -n 65536* and *ulimit -c unlimited*) . Second, when we upgraded to 6.3.5, IBM changed the startup script which further effects this.
On Mon, May 18, 2015 at 11:14 AM, Lee, Gary <[email protected]> wrote: > Servers running on redhat enterprise 6.1 and 6.5. > > Trying to set open files, max processes, etc for the dsmserv process. > > Tried using /etc/security/limits.conf, but no help. > Looking in /proc/process-id/limits > > Open files is 4096. > > However, set at 8192 for soft and 10240 for hard in > /etc/security/limits.conf. > > Any idea where the 4096 is coming from? > -- *Zoltan Forray* TSM Software & Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
