HI Gerald, That is a very offending line. We've removed it. Not only that, but Solaris usually doesn't start daemons (except the console) in that way. Solaris uses run control scripts. We put ours in /etc/init.d. It is pointed to from /etc/rc3.d which starts up when the system goes into multiuser mode. The script we use is:
# cat /etc/init.d/dsmcad_v1 #!/bin/sh DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt.v1 export DSM_CONFIG /bin/dsmcad-v1 -optfile=/opt/tivoli/tsm/client/ba/bin/dsm.opt.v1 > /var/log/nohup-v000 2>&1 & We call it from a link in rc3.d: lrwxrwxrwx 1 root other 21 Apr 19 16:24 S88dsmcad_01 -> /etc/init.d/dsmcad_v1 We also put in this line in the dsm.sys file: ManagedServices Schedule WebClient That way dsmcad runs the dsmc daemon by turning it on and off. This gets rid of the dsmc memory problem. Another reason we went to this solution is because we use console servers in order to do work from anywhere. Using that original inittab line actually hangs the console so you can't get into it from the console server, thus making the console server fairly useless. Hope this helps, -Bern -----Original Message----- From: Gerald Wichmann [mailto:[EMAIL PROTECTED]] Sent: Monday, May 13, 2002 4:34 PM To: [EMAIL PROTECTED] Subject: starting tsm server on solaris dsmserver:234:once:/opt/tivoli/tsm/server/bin/dsmserv >/dev/null 2>&1 Put that line into /etc/inittab but on reboot the TSM server doesn't come up.. I have to cd into the bin directory and manually start it.. I notice you have to set an environmental variable to start the tsm server from another directory other then it's installed directory but in order for it to work in inittab, I'm not sure where to put the environmental variable nor even if that's why it isn't starting (though I suspect it is why). Appreciate any help. Not used to solaris.. Regards, Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w)
