Date: Wed, 4 Dec 2002 12:12:41 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: Robert van Engelen <engelen@cs.fsu.edu> Cc: freebsd-arch@freebsd.org Subject: Re: Mac OS X BSD SO_NOSIGPIPE bug Message-ID: <Pine.BSF.4.21.0212041211010.26728-100000@InterJet.elischer.org> In-Reply-To: <7BF5285B-07A1-11D7-8EA1-000393C3075E@cs.fsu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 4 Dec 2002, Robert van Engelen wrote: Firstly, or course, a FreeBSD list is an odd place to ask a macOS question.. But, assuming that there might be an inherritted bug from FreeBSD, a sample test program would be a good start. > I recently ran into a nasty problem with BSD-based Mac OS X Darwin and > sockets with SO_NOSIGPIPE and SO_KEEPALIVE both enabled (setsockopt). > The problem is with bind(), accept() followed by multiple send() and > recv() calls. Eventually, the send() and/or recv() will stall for > several minutes, even though data is available. Monitoring the TCP/IP > traffic I found that the send() and/or recv() loops while attempting to > get more data or send data in 5 second intervals. Eventually this > succeeds after several minutes delay. The problem does not occur when I > use my own SIGPIPE signal handler, nor does it occur on Linux or other > UNIX platforms. I also removed the handler and all works fine in that > case as well. So even when the connections are not prematurely > terminated, the SO_NOSIGPIPE option causes this problem. Does anyone > have an idea? Has this behavior been observed before? Is this normal > behavior? > > - Dr. Robert van Engelen, Florida State University > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0212041211010.26728-100000>