The only really frustrating part was that nothing was written to the log file. When I woke up the next morning and fiddled with it a bit more, I realized that I could try running Tor through my local account and reference the suspect torrc file. When I did, it happily printed out the equivalent of "you didn't read the manual, dummy!" to stdout and quit right back to the command line. That led me to fixing the problem statement, and hence my the crashes.
I'd love to see Tor write all errors to the configured log file, including errors with the torrc file. And if logging isn't configured or is misconfigured, it might be appropriate to spit something into the default logging for the system (Windows Events, /var/log/messages, etc.). But for now, I'm willing to accept a resolution of "read the fancy manual."
-Lance On 25/11/2012 3:46 AM, Moritz Bartl wrote:
On 24.11.2012 17:28, Lance Hathaway wrote:Never mind, I figured it out. Apparently I had an invalid character in my Nickname, which caused Tor to dump itself without writing any sort of info to the configured log file. Looks good now.What kind of character did you use? Sounds like a good bug report.
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays