Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

globus-k5(8) [debian man page]

GLOBUS-K5(8)							  Globus Toolkit						      GLOBUS-K5(8)

NAME
globus-k5 - Acquire Kerberos Credentials for use with Grid Services SYNOPSIS
globus-k5 SERVICE-COMMAND [SERVICE-ARGS...] DESCRIPTION
The globus-k5 program is an authorization module used by the globus-gatekeeper program to acquire Kerberos 5 Credentials prior to executing a Grid Service. This may be accomplished by running kinit with a password stored in the globuskmap file, using the NCSA krb525 command, or the sslk5 command to use the X509 user proxy. The arguments passed to globus-k5 will not be used by it, but will be passed onto the job manager. The first parameter must be the path to the Grid Service. It is expected that the environment will contain the variables GLOBUSID and USER for the Grid and local POSIX user identities. This program is normally run as root, and will call seteuid() prior to executing the Grid Service. The parameters to use and the mapping for the globus to K5 user are located in the globuskmap file. FORMAT OF THE GLOBUSKMAP FILE
The globuskmap file is a line-oriented file which each line containing a command to run to acquire Kerberos 5 credentials for a Grid identity. Each line consists of an optionally-quoted GLOBUSID value followed by a command-line for running a process to acquire a Kerberos credential. For example: "/O=Example/OU=Grid/CN=Joe User" /usr/afsws/bin/klog -principal juser -password mypasswd -cell infn.it ENVIRONMENT
If the following variables affect the execution of globus-k5: GLOBUSKMAP Path to the globuskmap file. USER POSIX username that the service will run as. KRB5CCNAME Path to a Kerberos credential cache. GLOBUS_ID Grid identity to generate Kerberos credentials for. FILES
/etc/globuskmap Default file mapping Grid identities to Kerberos 5 principals. SEE ALSO
globus-k5(8), globus-job-manager(8) University of Chicago 01/06/2012 GLOBUS-K5(8)

Check Out this Related Man Page

GLOBUS-JOB-STATUS(1)						  GRAM5 Commands					      GLOBUS-JOB-STATUS(1)

NAME
globus-job-status - Check the status of a GRAM5 job SYNOPSIS
globus-job-status JOBID globus-job-status [-help] [-usage] [-version] [-versions] DESCRIPTION
The globus-job-status program checks the status of a GRAM job by sending a status request to the job manager contact for that job specifed by the JOBID parameter. If successful, it will print the job status to standard output. The states supported by globus-job-status are: PENDING The job has been submitted to the LRM but has not yet begun execution. ACTIVE The job has begun execution. FAILED The job has failed. SUSPENDED The job is currently suspended by the LRM. DONE The job has completed. UNSUBMITTED The job has been accepted by GRAM, but not yet submitted to the LRM. STAGE_IN The job has been accepted by GRAM and is currently staging files prior to being submitted to the LRM. STAGE_OUT The job has completed execution and is currently staging files from the service node to other http, GASS, or GridFTP servers. OPTIONS
The full set of options to globus-job-status are: -help, -usage Display a help message to standard error and exit. -version Display the software version of the globus-job-status program to standard output. -versions Display the software version of the globus-job-status program including DiRT information to standard output. ENVIRONMENT
If the following variables affect the execution of globus-job-status. X509_USER_PROXY Path to proxy credential. X509_CERT_DIR Path to trusted certificate directory. BUGS
The globus-job-status program can not distinguish between the case of the job manager terminating for any reason and the job being in the DONE state. SEE ALSO
globusrun(1) University of Chicago 03/18/2010 GLOBUS-JOB-STATUS(1)
Man Page