On Feb 9, 2006, at 2:37 PM, Ross Boylan wrote:
> On Wed, 2006-02-08 at 21:16 -0500, Brian Barrett wrote:
>> 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.
> Thanks. I've had one other thought. My test script executes before
> MPI_INIT is called--in fact, it's never called. Should I need to call
> MPI_INIT for stdin to be handled properly?
>
> Meanwhile, I see if I can get the beta installed.
In LAM/MPI, you standard input should be wired up at process launch
time -- calling MPI_Init is not required. Of course, some process
along the way has to call MPI_Init for other reasons, but that's a
different topic.
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
