URL: http://www.firstbasesoftware.com/man/man8/fblockd.htm
Last modified: 12 September 1995
Copyright © by FirstBase Software.
[ Index of Contents] [ FirstBase RDBMS Overview]

NAME

SYNOPSIS

DESCRIPTION

Here are a few lines that can be inserted in a UNIX startup file:

   FIRSTBASEHOME=/usr/local/firstbase; export FIRSTBASEHOME
   PATH=$PATH:$FIRSTBASEHOME/bin.`arch`; export PATH
   fblockd &

The fblockd process will listen for incoming requests from any FirstBase tool or application that requests a simple file lock or a database record lock.

To enable use of the FirstBase lock daemon, define the SERVER variable and set the LOCKDAEMON variable ON as described in setup(5).

The stderr stream is tied to the file specified via the FirstBase environment variable LOCKDERROR. Commands that cause errors to fblockd will generate their error messages into this file. Furthermore, fblockd needs only enough permissions to write into this error file -- it need not be setuid.

The FirstBase tool dblockmgr(8) can be used to examine locks. In addition, this tool can be used to set, clear, or monitor fblockd.

CAVEATS

In other words, the mount points for NFS shared file systems is crucial if you want to use fblockd. One very good method is to have all shared files available via a standard path name, like /net/machine_name/database/dbase. Another is to have one shared area, like /DATABASE, available from each machine.

When FirstBase files and databases are opened consistently across machines, fblockd can be used to handle locking requests. If this consistence is not possible, or you want to use the operating systems standard lock daemon (lockd(8)), set LOCKDAEMON to OFF.

FILES

fblockd.err - default error file

SEE ALSO

FirstBase User's Guide and Reference Manual