Bug 3935 - GRAM setup scripts must be run from $GLOBUS_LOCATION/setup/globus
: GRAM setup scripts must be run from $GLOBUS_LOCATION/setup/globus
wsrf scheduler interface
: 4.0.1
: All All
: P3 normal
: 4.0.2
Assigned To:
  Show dependency treegraph
Reported: 2005-11-23 11:55 by
Modified: 2005-12-06 09:16 (History)



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

Description From 2005-11-23 11:55:05
[globus@lucky0 globus-4.0.1]$
$GLOBUS_LOCATION/setup/globus/setup-globus-job-manager-pbs --
Error locating PBS commands, aborting!
[globus@lucky0 globus-4.0.1]$ cd $GLOBUS_LOCATION/setup/globus
[globus@lucky0 globus]$ ./setup-globus-job-manager-pbs --remote-shell=rsh
find-pbs-tools: WARNING: "Cannot locate mpiexec"
find-pbs-tools: WARNING: "Cannot locate mpirun"
checking for mpiexec... no
checking for mpirun... no
checking for qdel... /home/software/openpbs-2.3.16/bin/qdel
checking for qstat... /home/software/openpbs-2.3.16/bin/qstat
checking for qsub... /home/software/openpbs-2.3.16/bin/qsub
checking for rsh... /usr/bin/rsh
find-pbs-tools: creating ./config.status
config.status: creating

It looks like it's trying to run "find-pbs-tools" from the CWD:
print `./find-pbs-tools $non_cluster --with-cpu-per-node=$cpu_per_node
$remote_shell --cache-file

Seems like that should be "$GLOBUS_LOCATION/setup/globus/find-pbs-tools ..."

Or it could just chdir itself first.  It's non-intuitive that this script can't
be run from other dirs, even if 
the  documentation is written so that you would be in that dir.
------- Comment #1 From 2005-12-06 09:16:18 -------
committed fixes to 4.0 branch and trunk.