I have two freebsd boxes (back to back) and I've
been playing with a simple server on one machine
and client on the other machine (this was simply
an exercise with playing with kqueue). Both the
server and the client are single processes and the
client seems to stop at 32,763 connections.
I've
On Sun, 26 Jan 2003, Sam Tannous wrote:
> I have two freebsd boxes (back to back) and I've
> been playing with a simple server on one machine
> and client on the other machine (this was simply
> an exercise with playing with kqueue). Both the
> server and the client are single processes and the
On Sun, 26 Jan 2003, Sam Tannous wrote:
> I have two freebsd boxes (back to back) and I've been playing with a
> simple server on one machine and client on the other machine (this was
> simply an exercise with playing with kqueue). Both the server and the
> client are single processes and the cl
:
:> I have two freebsd boxes (back to back) and I've been playing with a
:> simple server on one machine and client on the other machine (this was
:> simply an exercise with playing with kqueue). Both the server and the
:> client are single processes and the client seems to stop at 32,763
:> con
Sam Tannous wrote:
> I have two freebsd boxes (back to back) and I've
> been playing with a simple server on one machine
> and client on the other machine (this was simply
> an exercise with playing with kqueue). Both the
> server and the client are single processes and the
> client seems to stop
Robert Watson wrote:
> Some of this has to do with limits on the available ancillary ports for
> out-going connections. Try adding additional IP addresses to the client
> machine, and forcing your client software to use specific IP addresses.
[ ... ]
> Hard-coding local addreses in your
> applic
6 matches
Mail list logo