Bug 3911 - Bug in GRAM documentation for Condor log file
: Bug in GRAM documentation for Condor log file
Status: NEW
: Documentation
Execution Management
: unspecified
: All All
: P3 normal
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-11-15 14:10 by
Modified: 2006-12-05 14:13 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-11-15 14:10:27
The administrator's guide's section on GRAM has a small bug in it. Specifically
the section on Scheduler-Specific Configuration Files:
http://www.globus.org/toolkit/docs/4.0/admin/docbook/ch11.html#s-wsgram-Interface_Config_Fragscheduler_specific_config

For globus-condor.conf, it says:

log_path
    Path to the SEG Condor log (used by the Globus::GRAM::JobManager::condor
perl module and Condor SEG module. The value of this should be the path to a
world-readable and world-writable file. The default value for this created by
the Fork setup package is $GLOBUS_LOCATION/var/globus-condor.log

There are three problems with this:

1) It's the Condor setup package, not the Fork setup package. 
2) The Condor setup package doesn't set it up. 
3) It defaults to $GLOBUS_LOCATION/tmp/gram_job_state/gram_condor_log

-alain