Garrett Wollman writes:
> > ISTR at one time you would instead get the actual sockaddr of the
> > just-closed socket, rather than a bogus sockaddr... and that is the
> > behavior one would expect.
>
> As itojun pointed out, accept() used to just block if the socket it
> thought it was going to give you turned out not to be there at the
> last moment. This was a killer for applications which expected
> return from select() to be a reliable indicator of connections
> waiting.
>
> I think the proposed fix is the best one we can get right now.
> Restructuring the TCP code to handle this case doesn't make a whole
> lot of sense to me (or apparently to itojun or jlemon either).
Ah, my apologies for being foggy on the prior behavior. Given the
circumstances, I agree returning the error from accept(2) seems
like the best option.
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
