On Sep 3, 2004, at 5:16 PM, William Boatin wrote:
>> 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.
If you signed up for the digests, that's all you get. :-)
This list is configured to "reply to list", not "reply to sender", so
when people reply, it goes to the list (not directly to you), and
therefore you get it in the digest whenever that is normally delivered
to you.
> [snipped]
> i dropped the '-x DISPLAY' from my mpirun line
> with a hostfile that looks like this:
> [snipped]
> wboatin_at_neuro-tom:~/search> mpirun c0 c1 c2 c3 -ssi rpi lamd -sf
> konsole_script ~/search/m
> [snipped]
> konsole: cannot connect to X server localhost:10.0
Thinking about this a little more, I realized that I hadn't had enough
caffeine earlier this morning when I answered you -- I misspoke. My
apologies.
Relaying your DISPLAY through ssh will not work -- I should amend the
FAQ to mention this. Note that the rest of this discussion (indeed,
this entire thread) really only applies to the rsh boot SSI module.
The issue is that X relaying through ssh is setup *for the duration of
the ssh command*. The ssh command is used to launch the remote LAM
daemons, but then it quits. Hence, as soon as lamboot has completed,
the DISPLAY environment variable in the lamd (and which is inherited by
MPI processes that the lamd starts) is stale and will not work (because
it refers to the ssh command/tunnel that no longer exists).
Sidenote: for processes on the origin, this is not the issue because
ssh was not used to launch that LAM daemon -- it was simply
fork/exec'ed into the background.
As such, as the FAQ mentions, you need to export your own DISPLAY
variable (sorry -- your using the -x DISPLAY should have reminded me of
this) that is set to some value that will work. For example (I'm a
tcsh guy):
setenv DISPLAY mycomputer.example.org:0
mpirun -x DISPLAY ....
You'll likely also need to use the xauth and/or xhost commands to give
the remote machines permission to write to your display (see their man
pages for details).
> however this gave the following error:
>
> wboatin_at_neuro-tom:~> ssh simba konsole
> konsole: cannot connect to X server
Based on my text above, this is now a moot point, but I'll give it a
shot anyway.
This depends on your default ssh setup on neuro-tom and the sshd setup
on simba -- whether they both allow X forwarding by default. If they
don't, you may need to use "ssh -X simba konsole".
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
