Bug #10338
Restart Tor if bootstrapping stalls for too long in bridge mode
0%
Subtasks
History
#1 Updated by anonym 2015-10-07 05:33:47
I think Feature #9516’s branch might have introduced a subtle issue: since we don’t restart Tor with restart-tor in bridge mode, Vidalia won’t be restarted if already running. In the automated test suite, there will be differences especially on snapshot, i.e. Vidalia will show a broken onion icon. No big deal, but we should try to come up with something that works consistently in each case.
Actually, maybe most logic (including tordate?) should be split out into restart-tor and some other helper scripts?
#2 Updated by anonym 2015-10-07 05:34:42
Or maybe we should just work until we have systemd and solve all his properly.
#3 Updated by anonym 2015-10-07 05:35:31
- Target version set to Tails_2.0
#4 Updated by intrigeri 2015-10-12 05:57:20
- Assignee set to anonym
> Target version set to Tails_2.0
Do you really mean it’s a blocker for 2.0 (which is what Target version == 2.0 means), or rather that we should not work on this on Tails/Wheezy?
#5 Updated by anonym 2015-10-12 06:03:43
- Target version deleted (
Tails_2.0)
intrigeri wrote:
> > Target version set to Tails_2.0
>
> Do you really mean it’s a blocker for 2.0 (which is what Target version == 2.0 means), or rather that we should not work on this on Tails/Wheezy?
The latter, so yes, this should be blocked by Feature #6171 instead. Thanks! The rationale for this blocker is, as you might suspect, that systemd probably will make this a lot easier to solve.
#6 Updated by anonym 2015-10-12 06:04:02
- blocked by
Feature #6171: Tails based on Jessie added