Re: cvs pserver performance

[Larry Jones]

Donald Sharp writes:
> 
> No I didn't contradict myself.  Perhaps I didn't fully explain...
> The kernel routes the socket data to inetd.  inetd manages the incoming
> and outgoing data from the sockets to different processes stdin and stdout.

That's not how it works.  The kernel routes data to and from a socket,
not a process.  Any process that has the socket open can read or write
it.  What inetd does is listen for connection requests.  When it
receives a connection request, it accepts the connection which creates a
brand new socket just for that connection.  inetd then starts the
appropriate server, giving it the new socket for its stdin, stdout, and
stderr.  inetd then closes the socket so that only the new server
process has the socket open.  The kernel routes data to and from the
socket and the server process reads and writes the data from the socket;
inetd isn't involved at all.

-Larry Jones

Why can't I ever build character in a Miami condo or a casino somewhere?
-- Calvin