Re: Should O_NONBLOCK be copied from listening socket to accepting socket?

Chris Evans <[EMAIL PROTECTED]> wrote: > Well, in our own manpages > man 7 socket >It is possible to do non-blocking IO on sockets by setting >the O_NONBLOCK flag on a socket file descriptor using >fcntl(2). O_NONBLOCK is inherited through an accept.

Re: Should O_NONBLOCK be copied from listening socket to accepting socket?

David S. Miller wrote: > Alexey tried to do this "fix" and when I tested his change we spotted > this issue and thus did not put the "fix" in what we sent to Linus. Is this patch available somewhere on the net? I really need it. - To unsubscribe from this list: send the line "unsubscribe

Re: Should O_NONBLOCK be copied from listening socket to accepting socket?

Chris Evans [EMAIL PROTECTED] wrote: Well, in our own manpages man 7 socket It is possible to do non-blocking IO on sockets by setting the O_NONBLOCK flag on a socket file descriptor using fcntl(2). O_NONBLOCK is inherited through an accept. Although

Re: Should O_NONBLOCK be copied from listening socket to accepting socket?

From: Michael Shields <[EMAIL PROTECTED]> Date:04 Sep 2000 20:27:53 + Is it required that the O_NONBLOCK flag be copied from a listening socket to an accepted socket? Dan Bernstein believes this is a bug. If we "fixed" this every inetd on every Linux system would

Re: Should O_NONBLOCK be copied from listening socket to accepting socket?

> Is it required that the O_NONBLOCK flag be copied from a listening > socket to an accepted socket? Dan Bernstein believes this is a bug. My posix 1003.1g draft leaves it undefined. It is possible that SuS clarifies this. Unless he can cite a SuS version that has clarified this I believe its

Should O_NONBLOCK be copied from listening socket to accepting socket?

Is it required that the O_NONBLOCK flag be copied from a listening socket to an accepted socket? Dan Bernstein believes this is a bug. Pavel Kankovsky writes: > What happens when x->tcpstate == 1 (i.e. waiting for the first byte of TCP > request length), x->io->revents == 0 (i.e. not ready

Should O_NONBLOCK be copied from listening socket to accepting socket?

Is it required that the O_NONBLOCK flag be copied from a listening socket to an accepted socket? Dan Bernstein believes this is a bug. Pavel Kankovsky writes: What happens when x-tcpstate == 1 (i.e. waiting for the first byte of TCP request length), x-io-revents == 0 (i.e. not ready for

Re: Should O_NONBLOCK be copied from listening socket to accepting socket?

From: Michael Shields [EMAIL PROTECTED] Date:04 Sep 2000 20:27:53 + Is it required that the O_NONBLOCK flag be copied from a listening socket to an accepted socket? Dan Bernstein believes this is a bug. If we "fixed" this every inetd on every Linux system would