Sam Locked

[Yan Wong]

Hi Folks,

I am running the SAM on X window. The SAM process gets terminated accidentally. There is a lock file under /var/sam/lock/lock_ttyqa. Before I rerun the sam, do I just simply remove this lock file?

Please advice.

[Steven E. Protter]

You got it, just get rid of the file

If you are paranoid like me, mv it some place.

The lock file is supposed to keep you from doing bad thigns with multiple copies of SAM running.

P

[Michael Tully]

Check to make sure that there are no 'sam' processes running first. If there, try to terminate them first. (Make sure that '/usr/lbin/sam/samd' is still there)

If there are none, yes you can go ahead and remove the lock file. (You may end up creating a core file as well, so look out for that.

[Rajeev Shukla]

Yes you can delete this file after confirming no one is running SAM.

Rajeev

[T G Manikandan]

Do you have the appropriate SAM patches in the system?

you have to check the /var/sam/log/samlog file for the errors that is causing the termination.

It is not a good idea of removing the lock file under /var/sam/lock.
This is because this lock file ensures that there are no two simultaenous SAM sessions.

Just check ps -ef|grep sam
whether any processes are running.
If some are running after termination it is better to kill the sam process.

But check the samlog and revert

[MANOJ SRIVASTAVA]

I would be more intrested in making the SAM run properly , or why does it accidentaly terminate , does this happen in non x windows mode , OS is pathced properly , the emulation on the node is standard etc stuff . Ofcouse the lock fiel can be deleted but the real solution would be why does the sam teminate


Manoj Srivastava