On Thu, Feb 03, 2005 at 05:44:26PM +0100, Gisle Vanem wrote:
> I was brought to the attention of Neon by someone trying to
> use it with djgpp and the Watt-32 tcp/ip stack. The assumption that
> all non-Win targets sets EPIPE (and also raises SIGPIPE) isn't
> correct AFAICS. From HP-UX's 'man send':
> ENOTCONN A send() on a socket that is not connected,
> or a send() on a socket that has not
> completed the connect sequence with its peer,
> or is no longer connected to its peer.
Can you describe precisely what problems were seen, and when the
ENOTCONN was triggered? It's important to be able to distinguish
between a *closed* and a *reset* socket. The above description could
mean anything really. Have you run "make check" on this platform?
neon mailing list