Hi Adam,
Thank you for that thorough and detailed explanation. I'd say 'guru' is not
much of an exaggeration, if any.
All best wishes,
Keith
Hi Keith,
I work with Zoltan here at Virginia Commonwealth University -- not sure if
"guru" is an accurate description! :-)
Here are the processes that I'm seeing when I grep for 'dsmserv' after the
update is applied:
root@processor ~ # ps -ef | grep dsmserv
root 4202 1 0 11:01 ?
> Op 12 dec. 2014, om 18:51 heeft Arbogast, Warren K het
> volgende geschreven:
>
> So Zoltan,
> What does your Linux guru have to say about the possible consequences of
> having the two processes running? Is it a neutral matter, or not?
>
> Thank you,
> Keith
in the past there was such a sm
So Zoltan,
What does your Linux guru have to say about the possible consequences of having
the two processes running? Is it a neutral matter, or not?
Thank you,
Keith
Hi Zoltan,
My hat is off to your LInux guru. I did notice that the ulimit commands have
been added to the dsmserv.rc file that comes with 6.3.5, but I had not put 2
and 2 together.
Best wishes,
Keith
My Linux guru has figured it out. IBM changed the *rc.dsmserv* script in
/opt/tivoli/tsm/server/bin to start dsmserv using the command "*su exec*"
versus just "*exec*". I think it is related to this apar:
http://www-01.ibm.com/support/docview.wss?uid=swg1IC90127
On Fri, Dec 12, 2014 at 10:09 AM
I just upgraded a Linux server from 6.3.4.200 to 6.3.5.100 and also see
2-dsmserv processes:
# ps -ef | grep dsmse
root 3008 1 0 10:05 pts/100:00:00 su - tsminst1 -c
/opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 -q
tsminst1 3103 3008 0 10:05 ?00:00:00
/opt/tivoli/t
Keith,
I'm running 6.3.5 on AIX, not RHEL, but I see only one dsmserv process. It's
possible something on the RHEL version changed at 6.3.5.
One thing I used to do in TSM 5 and earlier was add an "exec" to the
rc.dsmserv start script so it wouldn't leave the invoking rc script shell
lying around
I just updated a test TSM server from 6.3.4 to 6.3.5 on RHEL6. The post-startup
behavior of dsmserv seems to be diferrent.
__Our other 6.3.4 servers show one dsmserv process on a process list; like
this: ps -ef | grep dsm
tsm 16782 1 99 Nov28 ?29-07:37:33
/opt/tivoli/tsm/ser
