updating guard status from v2 networkstatuses?

[arma]

This is on my bridge, which is a relay plus dircache.

Nov 06 15:27:35.689 [info] connection_dir_client_reached_eof(): Received network
status objects (size 1729899) from server '128.31.0.34:9031'
Nov 06 15:27:35.720 [info] router_set_networkstatus_v2(): Setting networkstatus
downloaded from directory server "moria1" at 128.31.0.34:9031 (published 2007-11
-06 20:27:25)
Nov 06 15:27:35.803 [info] router_set_networkstatus_v2(): Setting networkstatus
downloaded from directory server "tor26" at 86.59.21.38:80 (published 2007-11-06

20:26:19)

Nov 06 15:27:35.886 [info] router_set_networkstatus_v2(): Setting networkstatus
downloaded from directory server "dizum" at 194.109.206.212:80 (published 2007-1
1-06 20:26:24)
Nov 06 15:27:35.967 [info] router_set_networkstatus_v2(): Setting networkstatus
downloaded from directory server "moria2" at 128.31.0.34:9032 (published 2007-11
-06 20:26:30)
Nov 06 15:27:36.048 [info] router_set_networkstatus_v2(): Setting networkstatus
downloaded from directory server "lefkada" at 140.247.60.64:80 (published 2007-1
1-06 20:26:49)
Nov 06 15:27:36.107 [info] entry_guards_compute_status(): Summary: Entry 'sabota
ge' is reachable, unusable and not live.
Nov 06 15:27:36.107 [info] entry_guards_compute_status(): Summary: Entry 'teunto
rt' is reachable, usable and live.
...

It appears to be not only caching the v2 networkstatuses, but also looking at them
and acting on them?

[Automatically added by flyspray2trac: Operating System: All]

[arma]

Fixed in r12479 (I hope)

[arma]

flyspray2trac: bug closed.