Hi Peter and Maarten,
Maarten Litmaath wrote:
> Some of the options are documented in this ticket:
> https://gus.fzk.de/ws/ticket_info.php?ticket=35835
Please be careful, because config options described there are for
globus-{job-manager|gass-cache}-marshal but NOT for globus-gma.
List of useful globus-gma options is as follows:
logf (string) - location of the log file, default is relative to
GLOBUS_LOCATION
groups (0 or 1) - set to 1 to also apply supplementary groups to job
poll process, default: 0
condorfix (0 or 1) - set to 1 to activate a Condor work-around for not
distinguishing VOMS attributes, default: 0
fileage (numeric) - after this number of seconds a job file is
considered 'stale' and gets removed, default: 86400
stateage (numeric) - for this number of seconds a job state is
considered 'fresh' and is not updated, default: 600
tick (numeric) - number of seconds between poll cycles, default: 300
tout (numeric) - single poll is allowed to run for this number of
seconds, default: 30
debug (numeric) - debug level, default: 0
> Look for errors in the globus-gma logs in /opt/globus/var/log;
> you can increase the debug level in /opt/globus/etc/globus-gma.conf
> and restart the daemon.
We should find a place to document it somewhere...
--
Cheers,
Andrey Kiryanov.
|