Hello,
I added the following two lines in the tsm startup script. the -n 8192 in
the startup script will start the process using the higher count number.
more /etc/init.d/tsminst1
start() {
# make sure that the server CAN create a core dump in the event of an error
# NAM - 16082014 - Added
Yep, we do the same thing. Note that /etc/security is only used by PAM, so
processes that don't descend from a PAM-managed login won't be affected by
it. This makes for an interesting problem where you will get different
limits for dsmserv if it's started during the system's boot process vs
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
Adding those lines worked.
Can one change the file /proc/pid/limits and change the limit for the running
dsmserv process?
I doubt it but thought I'd ask.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick
Marouf
Sent: Monday, May 18, 2015
