choose: sw hd | installObjy | setup: ams ls pud chs oids | confCH | maintain: ams ls pud chs oids | moveFD | creaBri

Search | Site Map .

Setting up lock server

What release should you use?

Lock server comes with the Objectivity release. The one from Objectivity should be used.

Other requirements


Where do I find installation files?


where $OBJYBASE is a directory where Objectivity has been installed.

What do I install?

Files used by the lock server include the following:

By default you do not need to move these files; they are part of Objectivity installation. At SLAC, we run lock server from a local disk (to avoid dependency on AFS - Objectivity binaries are stored in AFS). If you choose to avoid AFS dependency as well, make a directory on a local disk of each machine where lock server will run, and copy these three files to that directory.

Installing lock server

You will need to be root to do these steps.

Choose a machine to be your Objectivity lock server machine.

IMPORTANT: There is no security mechanism in Objectivity. Unless you setup a firewall to protect them, anyone in the world can connect to a port used by lock server. Therefore, you should never run lock server as root! Create a special UNIX user for running the Objy servers. If you can, block the lock server port at your firewall. Ask your gateway administrator.

Create the directory /usr/spool/objy directory and make it writable by the GID you are using for Objy. Then start the lock server with: $OBJYBASE/<arch>/bin/oolockserver. You should have the startup scripts of the machine automatically run this and it should be run as a user who can write to /usr/spool/objy. Also, the machine's shutdown scripts should run the ookillls command to try to safely shutdown the server.

Who to contact for problem resolution?

If you have problems, please contact Douglas Smith.


BaBar Public Site | SLAC | News | Links | Who's Who | Contact Us

Page Owner: Jacek Becla
Last Update: June 13, 2002