Jeff Kell ([log in to unmask]) wrote: : The client establishes a connection "s" with the server, then does uses : two fdopen() calls to open an input and and output path to the socket. : Consequently that happens to be where it's blowing up :-) : Can someone shed a definitive answer if this is legitimate Posix or not? Jeff, I don't have a definitive answer, but all I can say is that I don't recall fdopen() or associated stream functions being discussed as "supported" in the BSD Socket/iX manual (for MPE 5.0). I know that read() and write() are now documented as being supported for socket descriptors, as long as the application is POSIX -- whereas you used to have to use send[to]() and recv[from]() to do socket I/O. That leads me to believe that you can only use the I/O functions that are explicitly documented for sockets. I don't know enough to say why the streams functions blow up. If I get a chance (just got back from vacation and I'm still catching up), I'll do some digging and try to get you a better explanation. Peggy Bertsch HP Commercial Systems Division