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
