On Feb 3, 2006, at 7:25 PM, Ross Boylan wrote:
> After this I can type stuff in as if cat is operating. But when I hit
> ctl-D, I just see "^D" on the terminal. ctl-C does make everything
> abort. The file foo is empty, though perhaps if I typed enough I
> could
> get a buffer to flush.
>
> I noticed an earlier post
> (http://www.lam-mpi.org/MailArchives/lam/2005/02/9803.php) referred to
> some problems with the handling of stdin in 7.1.1, the version I'm
> running (on an Apple Darwin cluster, OS X Panther). Is that the
> cause,
> or something else?
If you are using LAM 7.1.1, standard input is going to be a bit more
broken than it should be. Could you try upgrading to LAM/MPI
7.1.2b31 from the URL below and see if it helps? I'm pretty sure it
will, but if not we'll have to do some more digging. The URL for the
beta is:
http://www.lam-mpi.org/beta/
> The manual and FAQ's about debugging all implicitly assume that
> getting
> control from the terminal is easy (or is it that they use X?); I'm not
> finding it so.
Most of the time, we do debugging by firing up gdb inside xterms so
that we can control each gdb / process individually. I believe this
is what we are referring to. However, when we don't have bugs in our
standard input setup, you should have no problems with the
configuration you are attempting.
> The real situation is more complex: mpiexec invokes a script, which
> invokes R. The R command is another script. Also, I'm often running
> inside various environments (e.g., I ssh to the cluster, run
> screen, and
> then run a shell inside emacs inside screen) that could interfere
> (though I've done the test without screen or emacs). Note that when I
> do cat > foo at the shell prompt, rather than launching mpi, ctl-D
> works
> as it should.
Yeah, you're definitely running into mpirun doing something wrong.
The only question is if we've already fixed it ;).
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
