How to kill a SAM session

[Ian Little]

Is it safe to kill a SAM session that has been started on a telnet session that has died. Which process should I kill?

ps -ef|grep sam

root 6219 6188 0 12:08:18 ? 0:00 sam /usr/sbin/sam
root 16851 16363 0 16:00:47 ttybb 0:00 grep sam
root 12545 6225 0 14:42:38 ? 0:00 sh -c LANG=C LC_ALL=C /usr/sam/l
bin/samx -C -p 6225 -s users
root 12546 12545 243 14:42:38 ? 20:32 /usr/sam/lbin/samx -C -p 6225 -
s users /usr/sam/lib/%L/ug.ui
root 6225 6219 0 12:08:19 ? 0:01 samx /usr/sam/lib/%L/fal.ui

[Pete Randall]

Ian,

I guess you don't have much choice so try "kill 6218 6225", then see what you have left. If the processes are still there, then try a kill -9.


Pete

[Robert-Jan Goossens]

Ian,

# kill 6219
# ps -ef | grep sam
# kill 6225

Regards,
Robert-Jan

[Marco Santerre]

I've done kills in the past on some SAM processes. Never had a trouble with it, but I guess it really depends what the person was doing in SAM, and there is no way of finding that out.

[A. Clay Stephenson]

Yes, you can kill the sam processes but you will then almost certainly need to remove any files under /var/sam/lock/ before another SAM session can be started.

[Pete Randall]

Ian,

My apologies - I should have said "kill 6219 6225" (not 6218).


Pete

[Michael Schulte zur Sur]

Hi,

have you trapped signal 1?
You will have to kill 6219 6225 12545 12546
First see, how far this process goes. Follow the pid, ppid as long as they refer to each other.

greetings,

Michael

[Ian Little]

Thanks everybody ... in the end I had to kill all 4 processes ... but it didn't cause a problem

[Shahul]

Hi,

Do a tail for /var/sam/log/samlog and find out what other session is doing. If he is not doing anything critical you can kill by using

#kill -9 6219

Then
#cd /var/sam/lock

Delete if any lock is there..

Hope this helps
Shahul