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 AT VM.MARIST DOT EDU] On Behalf Of
Nick Marouf
Sent: Monday, May 18, 2015 11:32 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] performance tuning tsm server
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 Ulimit 8192 for open files and -c unlimited for
core dump
ulimit -c unlimited
ulimit -n 8192
echo -n "Starting $prog instance $instance ... "
#if we're already running, say so
Hope that helps,
-Nick
On Mon, May 18, 2015 at 9:14 AM, Lee, Gary <glee AT bsu DOT edu> 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?
>
|