>By "new thread," do you mean a new thread on the mailing list archives? If
>so, it's probably >a function of your mailer. Most mail clients
>automatically put in the Right Headers when you >"Reply" to thread messages
>properly and our web archiver script (MHonArc) ususally >handles this
>properly.
about my new thread problem; i do mean a new thread on the mailing list
archive
i am not getting an email when people reply to a posting i made... i get the
daily digest, but not an email when somebody responds to a posting i made.
back to my problem:
>This is because you're exporting your DISPLAY variable.
>In an ssh world, you likely don't need to export DISPLAY because ssh will
>set it to a >relevant value in the remote shell. Most important: although
>it will be a different value than >what you have in the shell that you ran
>mpirun in, the output will still appear on your >screen.
>For example:
>shell$ ee
># launches the "ee" X program on your local display
>shell$ ssh other-machine.example.come ee
># if ssh is setup appropriately (and many systems do this by default), ee
>will be running on >other-machine but will appear on your local display
>rsh doesn't do this for you, which is why you typically either need to -x
>the DISPLAY (and >ensure that it's set to a value that is relevant on all
>nodes) or setup your "dot" files to do >the Right Thing (which is usually
>far more trouble than it's worth).
>So if you're using ssh, the solution here is likely to just drop the "-x
>DISPLAY" from your >mpirun command line.
i dropped the '-x DISPLAY' from my mpirun line
with a hostfile that looks like this:
tom cpu=3
simba cpu=2
tigger
stimpy
i ran this:
wboatin_at_neuro-tom:~/search> mpirun c0 c1 c2 c3 -ssi rpi lamd -sf
konsole_script ~/search/m
and got this:
Running konsole on neuro-tom
Running konsole on neuro-tom
Running konsole on neuro-tom
Running konsole on neuro-simba
konsole: cannot connect to X server localhost:10.0
-----------------------------------------------------------------------------
It seems that [at least] one of the processes that was started with
mpirun did not invoke MPI_INIT before quitting (it is possible that
more than one process did not invoke MPI_INIT -- mpirun was only
notified of the first one, which was on node n0).
mpirun can *only* be used with MPI programs (i.e., programs that
invoke MPI_INIT and MPI_FINALIZE). You can use the "lamexec" program
to run non-MPI programs over the lambooted nodes.
----------------------------------------------------------------------------
with just c0, c1 and c2 specified in the mpirun line, everything was fine.
fyi, i was able to run this successfully:
ssh -X simba konsole
however this gave the following error:
wboatin_at_neuro-tom:~> ssh simba konsole
konsole: cannot connect to X server
i do have the environment variable LAMRSH set :
wboatin_at_neuro-tom:~> echo $LAMRSH
ssh -X
which meams that LAM/MPI is using 'ssh -X' and not just ssh.
????
thanks
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee®
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
|
