Globus 2.4 Configuration Files
This appendix contains an overview of all the client and server configuration files.
GRAM has the following configuration files:
Here is the default globus-gatekeeper.conf:
-x509_cert_dir /etc/grid-security/certificates -x509_user_cert /etc/grid-security/hostcert.pem -x509_user_key /etc/grid-security/hostkey.pem -gridmap /etc/grid-security/grid-mapfile -home /usr/local/globus -e libexec -logfile var/globus-gatekeeper.log -port 2119 -grid_services etc/grid-services -inetd
-x509_cert_dirspecifies where to find the trusted CA certificates
-x509_user_certspecifies where to find the gatekeeper cert.
-x509_user_keyspecifies where to find the gatekeeper key.
-gridmapspecifies where to find the grid-mapfile
-homespecifies where the
-logfilevariables are relative to. By default, this is your
-especifies where to find scripts
-logfilespecifies where the gatekeeper should put its log.
-portspecifies what port the gatekeeper will run on.
-grid_servicesspecifies where the directory which contains the configured jobmanagers is.
-inetdspecifies that the gatekeeper should exit after dealing with one request. That is because inetd will launch a copy of the gatekeeper for every request that comes in to the port in
-port. If you are running a gatekeeper by hand, don't use this flag.
Here is an example globus-job-manager.conf:
-home "/home/bacon/pkgs/globus-2.4" -globus-gatekeeper-host bacon.mcs.anl.gov -globus-gatekeeper-port 2119 -globus-gatekeeper-subject "/O=Grid/O=Globus/CN=bacon.mcs.anl.gov" -globus-host-cputype i686 -globus-host-manufacturer pc -globus-host-osname Linux -globus-host-osversion 2.2.19-4.7mdk -save-logfile on_error -state-file-dir /home/bacon/pkgs/globus-2.4/tmp -machine-type unknown
See Job Manager Configuration for details. Note that the entries in this file are combined with the entries in $GLOBUS_LOCATION/etc/grid-services for any specific jobmanager.
$GLOBUS_LOCATION/etc/grid-servicescontains one file per configured jobmanager. The default jobmanager is contained in a file named "jobmanager". Here are the contents of an example file for a fork jobmanager:
stderr_log,local_cred - /home/bacon/pkgs/globus-2.4/libexec/globus-job-manager globus-job-manager -conf /home/bacon/pkgs/globus-2.4/etc/globus-job-manager.conf -type fork -rdn jobmanager-fork -machine-type unknown -publish-jobs
To install additional jobmanagers, you need to download the scheduler-specific jobmanager package.
The grid-mapfile specifies the list of authorized users of this resource. Each entry is a pairing of a subject name and a local user account.
The location of this file is specified in globus-gatekeeper.conf
MDS configuration files are described at the MDS Configuration page.
GridFTP has the following configuration files:
This follows the format of the Wu-FTP ftpaccess file. If GLOBUS_LOCATION is specified in the in.ftpd server's environment, or if you pass it the the -G <globus_location> flag, it will use the ftpaccess in $GLOBUS_LOCATION/etc, otherwise it will use /etc/ftpaccess.
This follows the format of the Wu-FTP ftpconversions file.
GridFTP uses the same authorization mechanism as describe in the GRAM mapfile, and uses the same /etc/grid-security/grid-mapfile.
Last modified: Fri May 10 10:58:39 CDT 2002