[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #2878 [Tor Client]: Confusing order of log messages if Tor is restarted after a some downtime

#2878: Confusing order of log messages if Tor is restarted after a some downtime
------------------------+---------------------------------------------------
 Reporter:  Sebastian   |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  major       |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by nickm):

  * priority:  minor => major
  * milestone:  Tor: 0.2.2.x-final => Tor: 0.2.3.x-final


Comment:

 One thing that might work here is to declare that if we start up with a
 consensus that we want to replace, don't declare ourselves bootstrapped
 until the download has succeeded or failed.

 We could also refrain from building user circuits until we have a recent
 consensus or have become persuaded that we won't get one.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2878#comment:2>
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