gx-watch-locks - Watch status of gx-map lock files
gx-watch-locks -help
gx-watch-locks -version
gx-watch-locks [options]
gx-watch-locks, part of the gx-map system, is an administrative command. It checks for the existence of lock files created by several gx-map commands.
The following commands currently create lock files:
Lock files are used to prevent more than one instance of a program from executing concurrently and possibly corrupting data files. If one of these commands dies or hangs for any reason, it can leave a lock file in place, preventing the same command from running again. This can freeze updates to the grid-mapfile or to the grid-security/certificates directory.
In some circumstances, a command can legitimately take a long time to execute, so the existence of a lock file doesn't necessarily indicate a problem. A lock file contains a brief message which includes a time stamp, the name of the program that created it, and the name of the host on which it's running. This should be examined to determine whether the lock is actually stale.
The gx-watch-locks command prints a list of current lock files. By default, lock files younger than 5 minutes are ignored, and the list is only displayed once. Command-line options can change this behavior.
Stale locks can be removed using the gx-remove-locks command (q.v.).
Option processing is done using the Perl Getopt::Long module.
Options may be specified with a single or double leading '-' character. Option names may be abbreviated to whatever is unique. Arguments may be separated either by a blank or by an '=' character. For example, ``-foobar 42'', ``--foobar=42'', and ``-foob 42'' would all be equivalent.
gx-map(7), gx-remove-locks(8), gx-ca-update(8), gx-check-index(8), gx-check-requests(8), gx-db-check-requests(8)
Keith Thompson, San Diego Supercomputer Center, <kst@sdsc.edu>
See the file LICENSE in the gx-map distribution, installed in the etc/gx-map subdirectory.