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, Zoltan Forray <[email protected]> wrote: > 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/1 00: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/tsm/server/bin/dsmserv -i /home/tsminst1 -q > > Has anyone determined if this is the new "normal"? > > > > > On Thu, Dec 11, 2014 at 2:50 PM, David Bronder <[email protected]> > wrote: > >> 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. IBM seemed to finally figure that out with 6.3.4, since >> they >> did the same thing in that version (maybe in earlier TSM 6, too; I went >> from >> 5.5 to 6.3.4). On 6.3.5 for AIX, the exec is still there, too. Maybe it >> got >> dropped somehow on the RHEL version of 6.3.5? >> >> =Dave >> >> >> On 12/11/2014 12:48 PM, Arbogast, Warren K wrote: >> > 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 >> > tsmXXXX 16782 1 99 Nov28 ? 29-07:37:33 >> /opt/tivoli/tsm/server/bin/dsmserv -u tsmXXXX -i /home/tsmbl01/tsmXXXX -q >> > >> > __The 6.3.5 server shows two dsmserv processes; the first one, owned by >> root, starts the second dsmserv process after 'su'ing to the instance >> owner, but, the first process continues running. >> > >> > root 10372 1 0 12:46 pts/0 00:00:00 su - tsmYYYY >> -c /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsmYYYY/tsmYYYY -q >> > tsmYYYY 10466 10372 0 12:46 ? 00:00:04 >> /opt/tivoli/tsm/server/bin/dsmserv -i /home/tsmYYYY/tsmYYYY -q >> > >> > __Is this new behavior, that the process owned by root continues >> running after starting the process owned by the instance owner? Or, did I >> overlook a configuration or permssion setting somewhere? >> > >> > Thank you, >> > Keith Arbogast >> > Indiana University >> > >> > >> >> -- >> Hello World. David Bronder - Systems >> Architect >> Segmentation Fault ITS-EI, Univ. of >> Iowa >> Core dumped, disk trashed, quota filled, soda warm. >> [email protected] >> > > > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > BigBro / Hobbit / Xymon Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > [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 > -- *Zoltan Forray* TSM Software & Hardware Administrator BigBro / Hobbit / Xymon Administrator Virginia Commonwealth University UCC/Office of Technology Services [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
