Custom Query (14830 matches)
Results (7 - 9 of 14830)
|#6998||not a bug||can't stop run as service||ANYONE!||barkway|
I never set Tor to run as a service. Somehow, it did it itself. I read the FAQ for how to stop it using command Tor --stop service (and Tor --delete service) but I get "Tor is not recognized as a service" from my Command Prompt. I NEED to stop this service running at startup because everytime my computer boots up I'm getting a message that my Tor is out of date (it's not) and needs to be updated.
|#1074||fixed||Tor sends clock_skew status event warn too liberally||AltF4||arma|
In command.c, if netinfo tells us our clock is skewed, we log based on:
But then we complain to the controller regardless of whether it's an authority:
So the simple fix is for 0.2.1.20 to only send the status event if severity == LOG_WARN.
Then Vidalia should workaround it by ignoring SOURCE=OR: clock skew events from Tor <= 0.2.1.19 and 0.2.2.1-alpha.
The broader challenge is that tor clients avoid going to the authorities, so if their clock is wrong, they'll never do more than log at log-level info, and all this status event work is for naught.
We should fix this in 0.2.2.x, either with a more aggressive proposal, or at least with a bit we remember that makes us connect to an authority (and thus get a trusted opinion on our time) if we keep getting skew problems from other relays.
[Automatically added by flyspray2trac: Operating System: All]
|#2639||duplicate||tor failing - NetBSD - Tor v0.2.3.0-alpha-dev (git-b3d74045ae79544f)||AltF4||yancm|
Starting within the last 24-36 hours, tor built from git starts, then exits without a core dump nor any warnings being logged. This is definitely new.
I've done a make clean/autogen/make install cycle with no change.