[GE users] Problems with LAM tight integration

slaton slaton at berkeley.edu
Mon Aug 7 01:33:31 BST 2006


Hi Reuti,

> This looks all fine. The first, i.e. local lamd, will be started from 
> the local hboot (without any rsh). Only the lamd-wrapper will make a 
> qrsh call. Can you put an echo in your lamd-wrapper with:

Here's the output from the lamd wrapper:

> echo "$@"

-H 10.0.1.9 -P 32778 -n 0 -o 0 -d -sessionsuffix sge-113-undefined

> echo $ENVIRONMENT

BATCH

> echo $PE

lam_tight_qrsh

I also added another debug statement to the lamd binary:

echo "will now exec $SGE_ROOT/bin/$ARC/qrsh -V -inherit -nostdin $HOSTNAME 
$LAMD_BINARY $@"

...this yields:

 will now exec /opt/sge/bin/lx24-amd64/qrsh -V -inherit -nostdin qcn15 
 lamd_binary -H 10.0.1.15 -P 32777 -n 0 -o 0 -d -sessionsuffix 
 sge-114-undefined

...which is really odd because the next line in the output file is:

 /opt/sge/bin/lx24-amd64/qrsh -V -inherit -n -p 32779 qcn15 exec 
 '/opt/sge/utilbin/lx24-amd64/qrsh_starter' 
 '/opt/sge/default/spool/qcn15/active_jobs/114.1/1.qcn15'
 
/opt/sge/bin/lx24-amd64/qrsh is a symlink to /opt/sge/bin/lx24-amd64/qsh.

thanks
slaton

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list