choose: sw hd | installObjy | setup: ams ls pud chs oids | confCH | maintain: ams ls pud chs oids | moveFD | creaBri
| |
|
|
choose: sw hd | installObjy | setup: ams ls pud chs oids | confCH | maintain: ams ls pud chs oids | moveFD | creaBri |
|
Maintaining lock server
Starting lock server
To run the lock server, type:
oolockserver
on the host where you want to run the server.
Starting of the Lock Server will fail if there is already a lock server running on the machine.
Stopping lock server
To stop the lock server, type:
ookillls
on the host where the server is running. Note: this will succeed only if there are no locks on the federation(s) it's serving.
It is not always possible to get rid of all locks, especially when there are many dead processes and oocleanup fails. In this case use the Unix kill command to terminate the lock server process.
Useful tips
- After starting the lock server, do oocleanup on the federations served by this lock server. It initiates the recovery of the federation.
- Watch the lock server size in memory. With time, It tends to grow (it scales with the number of served containers). Usually it needs to be restarted (for performance reasons) when it reaches physical memory size.
Related links
BaBar Public Site | SLAC | News | Links | Who's Who | Contact Us
Page Owner: Jacek Becla
Last Update: June 13, 2002