Libertas,
As I wrote to you earlier today, IPredator on Linux complained of similar
issues with excessive calls to time() under the Linux 3.x kernel series, but
not 2.6.
Let's track these issues in
https://trac.torproject.org/projects/tor/ticket/14056
as they appear to be quite similar.
I'd l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Resurrecting a thread from last year...
On 11/12/14 16:05, grarpamp wrote:
> On Thu, Dec 11, 2014 at 8:26 AM, Michael Rogers
> wrote:
>> * Which links should carry chaff?
>
> First you need it to cover the communicating endpoints entry links
> a
Is there a trick to writing to log files in windows 7?
The sample torrc file has this:
Log debug file @LOCALSTATEDIR@/log/tor/debug.log
I changed mine to this with no success:
Log debug file C:\tor\tor_debug.log
___
tor-dev mailing list
tor-dev@lists.
> I wonder if TIME_IS_FAST is being defined as 1 in any of these Linux or BSD
> builds.
I just found that the current OpenBSD release (5.6) has TIME_IS_FAST =
0. Details are in a ticket comment I just posted.
> Libertas, can you search your tor binary or tor debug symbols for the
> function "ap
To clarify, I used "strings /usr/local/bin/tor | grep approx_time".
signature.asc
Description: OpenPGP digital signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Also, I can do some testing with chutney on the OpenBSD VM in a few hours.
signature.asc
Description: OpenPGP digital signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> This little session at 31c3 may be of interest to anyone working on Tor
> Messenger. -Jeff
> >
> > https://events.ccc.de/congress/2014/wiki/Session:Messaging
> >
@Jeff: Is there a summary or notes from the session?
> You should think also RFC 1312 for message send protocol.
> It is old b
On Dec 31, 2014 10:38 PM, "Yawning Angel" wrote:
>
>
>
> I don't think we merged that branch yet, since it's not ready for
> general use. Additionally, it's not currently functional on the
> *BSDs. The KIST code last I checked only is used under Linux.
This is right; the KIST code is not curre
I'm working on question #2 now - I'm less well equipped to work on #1 at
the moment.
It's probably also worth mentioning that the dump with >400,000 calls to
gettimeofday() also had 30,714 calls to clock_gettime().
On 01/01/2015 03:47 PM, Nick Mathewson wrote:
>
> On Dec 31, 2014 10:38 PM, "Yawn
Hi Everyone, Happy New Year, first post to the -dev list but I've been
running some relays for months[1]. Overall a new user to Tor so feel
free to point me elsewhere if I'm asking poor questions.
I've noticed that the Tor Cloud project is dead in the water right
now. The last post on this list is
On 01/01/2015 08:07 AM, teor wrote:
> I'd like to get a sense of how many calls per second this represents.
> (400,000 would seem to be 100 to 1000 per second, unless you were debugging
> for a long while.)
My kdump suggested that there were almost 7,000 calls a second to
gettimeofday(). The deta
The Second International Conference on Electrical, Electronics, Computer
Engineering and their Applications (EECEA2015)
World Trade Center, Manila Philippines
February 11, 2015
University of Perpetual Help System Dalta, Las Piñas - Manila,
Philippines
February 12-14, 2015
http://sdiwc.net/co
On 01/01/2015 03:47 PM, Nick Mathewson wrote:
> What part of tor is accounting for all these time/gettimeofday calls?
I set up an OpenBSD 5.6 VM and built Tor 0.2.5.10 on it. I couldn't get
chutney working because of a number of strange errors that seemed
platform-specific, so I went for a less th
I also completely forgot to mention this comment:
https://trac.torproject.org/projects/tor/ticket/14056#comment:6
I'll look into doing the replacements. If anyone has concerns about
whether approx_time is exact enough, please let me know - I had never
heard of it previously. I'll look int
14 matches
Mail list logo
