GLOBUS-GRAM-AUDIT(8) GRAM5 Commands GLOBUS-GRAM-AUDIT(8)NAME
globus-gram-audit - Load GRAM4 and GRAM5 audit records into a database
SYNOPSIS
globus-gram-audit [--conf CONFIG_FILE] [[--create] | [--update=OLD-VERSION]] [--check] [--delete] [--audit-directory AUDITDIR] [--quiet]
DESCRIPTION
The globus-gram-audit program loads audit records to an SQL-based database. It reads $GLOBUS_LOCATION/etc/globus-job-manager.conf by
default to determine the audit directory and then uploads all files in that directory that contain valid audit records to the database
configured by the globus_gram_job_manager_auditing_setup_scripts package. If the upload completes successfully, the audit files will be
removed.
The full set of command-line options to globus-gram-audit consist of:
--conf CONFIG_FILE
Use CONFIG_FILE instead of the default from the
configuration file for audit database
configuration.
--check
Check whether the insertion of a record was
successful by querying the database after
inserting the records. This is used in tests.
--delete Delete audit records from the database right
after inserting them. This is used in tests to
avoid filling the databse with test records.
--audit-directory DIR Look for audit records in DIR, instead of looking
in the directory specified in the job manager
configuration. This is used in tests to control
which records are loaded to the database and then
deleted.
--query SQL Perform the given SQL query on the audit
database. This uses the database information from
the configuration file to determine how to
contact the database.
--quiet Reduce the amount of output for common
operations.
FILES
The globus-gram-audit uses the following files (paths relative to $GLOBUS_LOCATION.
etc/globus-gram-job-manager.conf
GRAM5 job manager configuration. It includes the
default path to the audit directory
etc/globus-gram-audit.conf
Audit configuration. It includes the information
needed to contact the audit database.
University of Chicago 08/30/2011 GLOBUS-GRAM-AUDIT(8)
Check Out this Related Man Page
globus_gram_job_manager_configuration(3) globus gram job manager globus_gram_job_manager_configuration(3)NAME
globus_gram_job_manager_configuration - Job Manager Configuration The Job Manager is generally configured using the setup-globus-gram-job-
manager setup script.
This section of the Job Manager manual describes all options which may be passed to the GRAM Job Manager in the configuration file
$GLOBUS_LOCATION/etc/globus-job-manager.conf.
Configuration File Options-k
Indicate that the job manager was built with the kerberos GSSAPI instead of GSI. This disables checks for a delegated GSI credential.
-home GLOBUS_LOCATION
Set the GLOBUS_LOCATION environment variable to the specified Globus-Location.
-target-globus-location GLOBUS_LOCATION
Set the GLOBUS_LOCATION environment variable to the execution node's GLOBUS_LOCATION, if different than the GRAM node's GLOBUS_LOCATION
-type JOB_MANAGER_TYPE
Set the type of scheduler interface to use for this job manager. A similarly named Perl module in the
$GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/ directory is needed.
-history PATH
Set the path to the directory to store job history files.
-cache-location PATH
Set the path for the GASS cache. This path must be unique for each user. RSL substitutions (such as /tmp/buildd and pbuilder) may be
used in this path. See RSL Substitions for a list of available RSL substitutions.
-extra-envvars VAR1[=VAL],VAR2,...
The Job manager will attempt to get the listed VARs from its environment and set them the same for the job's environment. For example,
-extra-envvars LD_LIBRARY_PATH,GLOBUS_TCP_PORT_RANGE
-scratch-dir-base PATH
Set the default scratch directory root for the job manager. Job-specific scratch directories will be created as a subdirectory of this
directory. RSL substitutions (such as /tmp/buildd and pbuilder) may be used in this path. See RSL Substitions for a list of available
RSL substitutions. If this option is not present in the configuration file, then the job manager will create scratch directories as
subdirectories of the user's home directory.
-condor-arch ARCH
Set the condor architecture for this job manager to be the specified ARCH. This is optional when the job manager type is condor.
-condor-os OSNAME
Set the condor operating system name for this job manager to be the specified OSNAME. This is optional when the job manager type is
condor.
-globus-gatekeeper-host HOST
Set the name of the gatekeeper host. This will be made available in the GLOBUS_GATEKEEPER_HOST RSL substitution.
-globus-gatekeeper-port PORT
Set the TCP port of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_PORT RSL substitution.
-globus-gatekeeper-subject SUBJECT
Set the GSI subject name of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_SUBJECT RSL substitution.
-globus-host-manufacturer MANUFACTURER
Set the manufacturer name of the host machine. This will be made available in the GLOBUS_HOST_MANUFACTURER RSL substitution.
-globus-host-cputype CPUTYPE
Set the cpu type of the host machine. This will be made available in the GLOBUS_HOST_CPUTYPE RSL substitution.
-globus-host-osname OSNAME
Set the operating system name of the host machine. This will be made available in the GLOBUS_HOST_OSNAME RSL substitution.
-globus-host-osversion OSVERSION
Set the operating system version of the host machine. This will be made available in the GLOBUS_HOST_OSVERSION RSL substitution.
-globus-tcp-port-range RANGE
Set the range of TCP port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_PORT_RANGE
environment variable and RSL substitution.
-globus-tcp-source-range RANGE
Set the range of TCP source port numbers which the job manager will use. This will also be made available in the
GLOBUS_TCP_SOURCE_RANGE environment variable and RSL substitution.
-state-file-dir PATH
Set the path to store job manager state files (used for restarting a job manager which fails). If this is not set, then job state files
will be stored in the $GLOBUS_LOCATION/tmp/gram_job_state directory.
-x509-cert-dir PATH
Set the path to the X.509 trusted certificate directory on the job execution hosts. If not present, then the trusted certificate
directory used by the job manager (usually set by the Gatekeeper) will be used
-seg-module MODULE
Use the named module as a way to interact with the scheduler instead of polling for job status.
-audit-directory DIRECTORY
Store job auditing records in DIRECTORY. This directory should be sticky and group writable but not group readable. Audit records can
be uploaded to a database by using the globus-gram-audit command.
-globus-toolkit-version VERSION-STRING
Use the string VERSION-STRING as the toolkit version in audit records.
-enable-syslog
Send log messages to the system log.
-stdio-log LOG_DIRECTORY
Obsolete way to set the directory for writing log messages. Messages will be written to LOG_DIRECTORY/gram_DATE.log. Use -log-pattern
instead
-log-pattern PATTERN
RSL-substituted pattern for naming log files. Possible variables are HOME, LOGNAME, DATE. The -stdio-log is equivalent to -log-pattern
/tmp/buildd/gram_.log
-log-levels [FATAL|ERROR|WARN|DEBUG|INFO|TRACE]
List of log levels to enable site-wide. These may be joined by the '|' character.
Version 13.33 Mon Apr 30 2012 globus_gram_job_manager_configuration(3)