[PROXYPER] Proxyper not accepting connections.
jlawson at bovine.net
Sat Jan 23 19:59:27 EST 1999
I suspect the problem is really that you have the connectperiod set so
short that it leaves no time for clients to connect. The proxy is single
threaded with all operations (except DNS lookups) performed in
non-blocking operation. If the proxy is busy attempting to do a DNS
resolve, the resolution will not time out until the OS-defined timeout
occurs. By that time, the connectperiod may have already passed, and the
proxy will immediately decide that it needs to try another connection
The resolution is to set your connectperiod larger, or set the proxy in
offline (or lurkonly on win32) mode.
Jeff Lawson http://www.cs.hmc.edu/~jlawson/ http://www.bovine.net/
Jeffrey_Lawson at hmc.edu jlawson at bovine.net bovine at distributed.net
Programmer, Developer, Mascot, Founder of the largest computer on earth!
Don't waste those cycles! Put them to use! http://www.distributed.net/
On Fri, 22 Jan 1999, Michael Hannigan wrote:
> I have the same problem. When the out buffer is over the maximum number, it
> will no longer accept connections. It will flush once I go online and then
> resume normal operation, but prior to that, my clients work on random
> -----Original Message-----
> From: owner-proxyper at lists.distributed.net
> [mailto:owner-proxyper at lists.distributed.net] On Behalf Of Paul Comfort
> Sent: Friday, January 22, 1999 8:06 AM
> To: proxyper at lists.distributed.net
> Subject: Re: [PROXYPER] Proxyper not accepting connections.
> At 09:59 AM 1/22/99 +0000, you wrote:
> >Linux, build 302.
> Upgrade to 303 if possible.
> >Hmmm, I'm running proxyper on a dialup and it's serving it's own client and
> >another client, but when proxyper is trying to contact the outside world
> >(and failing, it's in lurkonly mode) it will refuse to handshake with the
> >clients - thus one machine has been working on random blocks all night even
> >though the proxy seems to have 16 blocks to pass on.
> I run the same config (linux and dialup build 303) but with a few more
> machines here. I don't run lurkonly though, just leave it normal and make
> sure I have enough blocks on hand. With this configuration you should
> never have a problem. You can also kill -ALRM it to make it flush when you
> go online if that is the reason you wanted lurkonly.
> To unsubscribe, send 'unsubscribe proxyper' to
> majordomo at lists.distributed.net
> To unsubscribe, send 'unsubscribe proxyper' to majordomo at lists.distributed.net
To unsubscribe, send 'unsubscribe proxyper' to majordomo at lists.distributed.net
More information about the proxyper