gx-db-check-requests - Process requests for TGCDB updates
gx-db-check-requests -help
gx-db-check-requests [options]
gx-db-check-requests is part of the gx-map system and of the optional TGCDB (TeraGrid Central Database) subsystem. This subsystem specific to the TeraGrid; it may or may not be installed on your system.
gx-db-check-requests is normally run from a cron job. It checks for new db-request files generated by gx-db-request.
The gx-db-check-requests command must be executed by the account that owns the gx-map installation; this is typically the ``gxmap'' or ``globus'' account, but a different account can be configured when the gx-map system is installed.
There are three kinds of db-requests, described in more detail in the gx-db-request(8) man page.
The gx-db-check-requests command maintains a file, gx-map-data/tgcdb-mappings, which contains (a close approximation of) the set of username/DN mappings currently stored in the TGCDB. It uses this to track any changes and invoke the gx-request command as needed.
For an add or remove request, the specified mapping or mappings are added to or removed from the tgcdb-mappings file.
For a full-query request, gx-db-check-requests performs a full query of the TGCDB to obtain a list of all current mappings, and replaces the tgcdb-mappings file with this list.
In any case, the new tgcdb-mappings file is compared to the saved
previous version. The gx-db-check-requests command then invokes
gx-request -add ... or gx-request -remove ... for each change.
The effect of this is to keep the gx-map system's idea of what
mappings currently exist synchronized with the information in the
TGCDB.
Once a db-request file has been processed, it is moved from the gx-map-data/new-db-requests directory to the gx-map-data/old-db-requests.
The gx-db-check-requests command can be invoked periodically from a cron job, or it can be invoked immediately after gx-db-request is executed. The two commands are separate because gx-db-request might be invoked asynchronously, and because it can be more efficient to invoke gx-db-check-requests once after several invocations of gx-db-request.
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-db-request(8), gx-propagate(8), gx-map-db-config(5)
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.