[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor 0.1.2.2-alpha eventdns timeouts
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Tor 0.1.2.2-alpha eventdns timeouts
- From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
- Date: Fri, 8 Dec 2006 01:10:20 -0500
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Fri, 08 Dec 2006 01:11:55 -0500
- In-reply-to: <20061026184957.69202a48@localhost>
- Mail-followup-to: Nick Mathewson <nickm@xxxxxxxxxxxxx>, or-talk@xxxxxxxxxxxxx
- References: <20061023124848.35580f5f@localhost> <20061023225433.GC13568@totoro.wangafu.net> <20061026184957.69202a48@localhost>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Mutt/1.4.2.1i
On Thu, Oct 26, 2006 at 06:49:57PM +0200, Fabian Keil wrote:
[...]
> As a result I see indeed a lot less timeout warnings,
> and the servers are declared active right away, but it
> also looks as if the number of timeouts isn't reset
> correctly:
My apologies for the delay here. Your diagnosis turned out to be
completely correct. I was looking for far more tricky problems, when
the root cause turned out to be (I think) that eventdns.c never
actually reset the timeout count. Oops! I've checked a patch in to
subversion as r9054; if you have a chance to see whether it fixes the
problem for you, I'd be most grateful.
yrs,
--
Nick Mathewson
Attachment:
pgprUQozHKwmz.pgp
Description: PGP signature