Hi Andre I am also looking for solution to this problem, but its seems that no body replied to this problem. If you have already solved the problem, Please let me know. Regards Kashif
________________________________ From: [email protected] on behalf of Andre Charbonneau Sent: Thu 3/19/2009 1:53 PM To: [email protected] Subject: [gt-user] questions about PBS scheduler adapter Greetings, I have a few questions regarding the PBS job manager in Globus. I'm currently running Globus 4.0.8 on a computational cluster. On the head node, Globus is installed under /usr/local/globus-4.0.8, and on the worker nodes Globus is installed under /opt/globus. We noticed that the PBS jobs were failing if we were trying to access the GLOBUS_LOCATION variable within the job. After investigating a bit more into this, it looks like the PBS scheduler adapter puts the following in the PBS job script: GLOBUS_LOCATION=/usr/local/globus-4.0.8 export GLOBUS_LOCATION The GLOBUS_LOCATION path above is taken from the head node, so when the job runs on the work node (where Globus is in /opt/globus) any references to $GLOBUS_LOCATION will fail. - So this means that Globus 4.0.x assumes that the cluster's head node and work nodes have the same value for GLOBUS_LOCATION, right? - Is there a configuration parameter that can be set that would prevent the PBS scheduler adapter from putting the above lines in the PBS script? - Is this assumption also made in Globus 4.2.x? Any information about this would be much appreciated. Best regards, Andre
