[tor-bugs] #4011 [Tor Relay]: 0.2.3.3 relay won't fetch microdesc consensus on startup if it already has a normal consensus

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#4011: 0.2.3.3 relay won't fetch microdesc consensus on startup if it already has
a normal consensus
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:                    
     Type:  defect     |         Status:  new               
 Priority:  major      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Relay  |        Version:  Tor: 0.2.3.3-alpha
 Keywords:             |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------
 In networkstatus.c we have:
 {{{
 /** A time before which we shouldn't try to replace the current consensus:
  * this will be at some point after the next consensus becomes valid, but
  * before the current consensus becomes invalid. */
 static time_t time_to_download_next_consensus = 0;
 }}}

 which we use in update_consensus_networkstatus_downloads() to decide
 whether to break out:
 {{{
   if (time_to_download_next_consensus > now)
     return; /* Wait until the current consensus is older. */
 }}}

 The result is that we don't even try to fetch a microdesc consensus if the
 ns consensus we have is recent enough.

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