Re: lib/45564: 2nd socket created by socketpair(2) is not connected to 1st socket.

[Matthew Mondor <mm_lists%pulsar-zone.net@localhost>]

The following reply was made to PR lib/45564; it has been noted by GNATS.

From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: lib/45564: 2nd socket created by socketpair(2) is not connected
 to 1st socket.
Date: Fri, 4 Nov 2011 13:02:10 -0400

 On Fri,  4 Nov 2011 17:00:07 +0000 (UTC)
 Matthew Mondor <mm_lists%pulsar-zone.net@localhost> wrote:
 
 >  Does this still happen if you remove SOCK_CLOEXEC from the protocol
 >  argument to socketpair(2)?  If it no longer occurs without the
 >  SOCK_CLOEXEC, fcntl(2) could be used to later enable close-on-exec
 >  instead.
 
 Err, of course I meant the type argument.
 -- 
 Matt