[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2149 [Tor Client]: new 'extra dormant' mode for people who never use their tor
#2149: new 'extra dormant' mode for people who never use their tor
---------------------------------+------------------------------------------
Reporter: arma | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Tor: 0.2.4.x-final
Component: Tor Client | Version:
Keywords: performance scaling | Parent:
Points: | Actualpoints:
---------------------------------+------------------------------------------
Comment(by sysrqb):
I finally finished a prelim patch for this. It can be pulled from branch
bug2149 on [http|git]://gitweb.evolvesoftware.cc/tor.git
I used the staged idea, mentioned above, in order to steer clear of
storing timestamps. Obviously this won't be as accurate, and if the client
is completely unstable and is never alive for longer than the stage size
(two hours right now) then the client will never go dormant. We can always
decrease the stage size to a smaller period.
I added a catch in conn_read_callback that checks if the client is
currently dormant; if it is, then it pulls updated descriptors/network
status before proceeding to handle the new connection.
While the client is dormant, I mostly ANDed the checks for
options->DisableNetwork with directory_too_idle_to_fetch_consensuses
throughout second_elapsed_callback and run_scheduled_events (with a few
additions). Are there other ways that the consensus can be pulled that
bypasses the callback?
Thanks for any feedback!
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2149#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs