David Thompson:
|> Here's a patch to 3/2/01 CVS which beefs up Distributed DX a bit.
|>These were made to get our IBM SP nodes crunching DX from our SGIs using
|>Execution Groups.
|>
|
|Wow, this is a great patch. I've been trying to find time to get dx
|set up to use ssh--now I don't have to. Could you send the patch to
|me again personally Randall, I can't get it decompress--it looks like
|it may have gotten mangled by sendmail somewhere along the line. Then
|I'll have some questions for you.
Thanks.
That file corruption is odd. I mailed the file to myself, and it's
uncorrupted, but the one I just saved from the dx-dev broadcast of my post
has an extra linefeed (0x0a) at the end of the saved .gz datafile --
strange. Probably could just trim the last byte off the file, but I'll
e-mail you an ASCII version of the patch just in case.
Here's an example dx_rsh script I use (machine names changed to protect the
innocent). My .cshrc has:
setenv DX_RSH $HOME/bin/dx_rsh
setenv DX_RSH_NOENV
------------------------------------------------------------------------------
#!/bin/sh
#
# dx_rsh - OpenDX rsh wrapper for running distributed DX.
#
# Set your $DX_RSH env to point to this script. Then tell this
# script how to initiate remote commands on a system, given the
# hostname in $1.
#
HOSTNAME=$1
HOST=`echo $HOSTNAME | cut -f1 -d.`
DOMAIN=`echo $HOSTNAME | cut -sf2- -d.`
CMD=rsh
if [ "$DOMAIN" == sub1.company.com -o "$DOMAIN" == sub2.company.com -o \
-z "$DOMAIN" ]; then
case "$HOST" in
host1*|host2*|host3|host4)
CMD=ssh;;
esac
fi
exec $CMD "$@"
------------------------------------------------------------------------------
Randy
--
Randall Hopper (mailto:[EMAIL PROTECTED])
Lockheed Martin Operation Support
EPA Scientific Visualization Center
US EPA MD/24 ERC-1A; RTP, NC 27711
