Re: [OMPI users] pipe function call failed...

2010-03-09 Thread Ralph Castain
On Mar 9, 2010, at 7:26 PM, Lasse Kliemann wrote: > Thanks for your help, Ralph. > > --disable-pty-support indeed makes the problem go away. > > The system is self-made and non-standard. I have in my kernel > config: > > CONFIG_UNIX98_PTYS=y > # CONFIG_LEGACY_PTYS is not set > > Maybe legacy

Re: [OMPI users] pipe function call failed...

2010-03-09 Thread Lasse Kliemann
Thanks for your help, Ralph. --disable-pty-support indeed makes the problem go away. The system is self-made and non-standard. I have in my kernel config: CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set Maybe legacy PTYs are required? Moreover, the system uses UDEV (version 151). I presu

Re: [OMPI users] pipe function call failed...

2010-03-09 Thread Ralph Castain
Okay, I dug thru the glibc 2.11 manual - there doesn't appear to be any problem here in the code itself. The problem instead, I believe, is caused by your system not supporting pty's, yet you are trying to use them. In this case, tcgetattr will return errno 22 because the file descriptor is not

Re: [OMPI users] pipe function call failed...

2010-03-09 Thread Lasse Kliemann
Alas, I am by far no Glibc expert. I did a grep through the Glibc changelog, but only found a reference to tcgetattr from 2006. Of course, I would also like to see a real solution here instead of ignoring the error condition. * Message by -Ralph Castain- from Tue 2010-03-09: > Ignoring an error

Re: [OMPI users] pipe function call failed...

2010-03-09 Thread Ralph Castain
Ignoring an error doesn't seem like a good idea. The real question is why we are getting that error - it sounds like the newest Glibc release has changed the API?? Can you send us the revised one so we can put in a test and use the correct API for the installed version? On Mar 9, 2010, at 9:40

[OMPI users] pipe function call failed...

2010-03-09 Thread Lasse Kliemann
$ mpirun -n 1 ls -- mpirun was unable to launch the specified application as it encountered an error: Error: pipe function call failed when setting up I/O forwarding subsystem Node: x.xx..xx while attempt