On Fri, 15 Sep 2000, Michael Poole wrote:
> Most of the programs called by inetd don't expect non-blocking I/O on
> their stdin and stdout, which they would suddenly get if accept()'ed
> sockets inherited the non-blocking nature of inetd's listening socket.
Looking at nkit 0.4.2, I cannot see a thing such as a non-blocking
listening socket (name the line if there is). Where does inetd set its
listening sockets to O_NONBLOCK? Why should an application that
originates on BSD misbehave if it got BSD semantics?
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
