Prabhanjan Kambadur wrote:
>>I think some people have seen this problem before. I see it on Cygwin
>>1.5.5-1. I use an xterm and start "lamboot" in a separate window, but
>>have tried the regular Cygwin prompt etc. I've read the postings by
>>Prabhanjan Kambadur et al.
>>
>>
>>
>
>I am not sure if I understand your mail properly. Does you badness occur
>when you run on native terminals or on xterm? I understand that you
>lambooted using "xterm". But did you run the commands using the regular
>Cygwin prompt?
>
>Assuming that you ran the commands on native terminal and the "xterm"
>which was used for "lamboot" was invoked from the same native terminal, it
>would not work as there still would be a parent child relationship
>between the terminals. I suggest that you run everything on xterm and let
>me know (assuming it was not done already).
>
>Anju.
>
>
>
>>I try the following:
>>$ mpirun -v C hello.exe
>>mpirun (set_stdio): Connection aborted
>>
>>And then using the -f flag:
>>$ mpirun -v -f C hello.exe
>>3512 hello.exe running on n0 (o)
>>
>>And then using mpiexec:
>>$ mpiexec -d -v -n 1 hello.exe
>>mpiexec: Global argument parsing done
>>mpiexec: Host-Node Number hash created
>>mpiexec: Temporary file lam_appschema_Ko9g5G created (will be used as
>>app schema file for mpirun)
>>mpiexec: Launching MPI programs
>>mpirun (set_stdio): Connection aborted
>>mpiexec: Inside handle_waitpid_status Function: mpirun, Error Status: 28928
>>mpiexec: mpiexec_die called
>>mpiexec: deleting temprory file lam_appschema_Ko9g5G
>>mpirun failed with exit status 113
>>
>>I have no problems running hello.exe on Linux. Is there a description of
>>what is happening here?
>>
>>Thanks alot
>>
>>chrisb
>>
>>
>>
>
>
>
Thanks Anju for getting back to me so promptly.
I ran all combinations of xterm and cygwin native prompt as per the
email discussion surrounding the posting by Prabhanjan Kambadur et al.
Just tried it again this morning:
1) Start Cygwin native prompt
2) run "startx"
3) In X open 2 xterms
4) In xterm A, run "lamboot hostfile"
5) In xterm B, run "mpirun C hello.exe"
The above steps give the error "mpirun (set_stdio): Connection aborted"
If I use the -f option then it sort of works, with the output appearing
in xterm A. I'm looking for some pointers to information explaining what
is going on here so I can understand how this behaviour will effect the
code I will write. Is this a bug? Why is there no -f option for
"mpiexec"? Why does the -f option semi fix the problem?
Thanks alot
chrisb
|
