Re: kern/54650: Calling accept() with a non-blocking listening socket, returns a non-blocking connected socket, which is incorrect behaviour

[Martin Husemann <martin%duskware.de@localhost>]

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

From: Martin Husemann <martin%duskware.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/54650: Calling accept() with a non-blocking listening
 socket, returns a non-blocking connected socket, which is incorrect
 behaviour
Date: Sun, 27 Oct 2019 08:27:29 +0100

 On Sat, Oct 26, 2019 at 06:37:47PM -0400, Christos Zoulas wrote:
 > Linux is unique in that behavior. All the BSDs (including MacOS) and Solaris return a non-blocking socket.
 
 I think it is also documented in accept(4):
 
 	... creates a new socket with the same
      properties of s and allocates a new file descriptor for the socket.
 
 Where I read "same properties" as including the socket options.
 
 Martin