[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down
#8001: obfsproxy makes tor warn when one bridge is down
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.4.x-final
Component: Tor | Version:
Keywords: tor-client | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by arma):
Replying to [comment:1 dcf]:
> Do you suggest that the "bridge down" message be [info], with a [warn]
only if all bridges for all transports fail, i.e., if we have no
connectivity at all?
That is what I was thinking, yes.
Quoting from
https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#WhatloglevelshouldIuse
:
"warn": something bad happened, but we're still running. The bad thing
might be a bug in the code, some other Tor process doing something
unexpected, etc. The operator should examine the message and try to
correct the problem.
If the operator had selected these bridges herself, I could see a warn
here. But since they come prechosen, and there are many of them exactly to
tolerate some being down, it doesn't seem like something the user needs to
know about.
That said, there's a messy race condition here: if the down one is the
first one we try, there aren't any working at the time, so we would end up
warning anyway. I'm not sure how to fix.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8001#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