[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: clock jump in 0.2.0.23-rc, too
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: clock jump in 0.2.0.23-rc, too
- From: coderman <coderman@xxxxxxxxx>
- Date: Sat, 5 Apr 2008 19:49:46 -0700
- Cc: or-talk@xxxxxxxx
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Sat, 05 Apr 2008 22:49:55 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=jWbf5GILDjJk7mxVEcw/sNoA6vukjjuzH0dNR/MWLOM=; b=Rb0925M8XwoFKYy6EJKNuGsMFBuhoBMOd1LA+iYeIbvaZMBTGRTyH03LmgyOf59OO130M6vdtfzIU2yqhGXnOZhlMKXgVuAGZQ6h38nQM8awxKtgLkP0a8S7U9qKJFxFqW0zy2THXGk+YaEPV6/85WSsTU/yGZu7Smb1kJfSsbA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ko4b8ebG6bEPCoAedgn7oju6//Ytd5EM22UI2L2rbkAFPtBucCsiBGvrkfuypy5ZUkgkbg8LHHIEaFZqvN9Vcrs3W52Yod6TZ+7AC8IWpC0/zU5sbli4NKRDfTT+9dWc52fpPOj79CDaSXpxdvTk7A2FXZXmk5mje+dAakIvqNU=
- In-reply-to: <200804052047.m35KlU0E020283@xxxxxxxxxxxxx>
- References: <200804052047.m35KlU0E020283@xxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
On Sat, Apr 5, 2008 at 1:47 PM, Scott Bennett <bennett@xxxxxxxxxx> wrote:
> ... Here is some of yesterday's notice-level log from my tor (0.2.0.23-rc) ...
> Those are all of the messages issued thus far, so 0.2.0.19-alpha has been
> running with no problems for over 25 hours. I will continue to watch the list
> for news of a new release to try, but for now, the *-rc versions are quite
> unusable as servers.
i'm curious to know if your configure script is perhaps doing
something wonky; can you determine if there are changes in the link
flags, config.h, or -D defines between these two versions that
configure may be generating?
in particular, i'm curious if something in a failed configure setup is
causing your tor_gettimeofday wrapper to use ftime() instead of
gettimeofday().
best regards,