Re: [tor-talk] NT Service installation does not handle ``bridge relay'' option in torrc file

[Moses <moses.mason@xxxxxxxxx>]

I've tried this but with no luck. The problem is, after running either
> tor --service install -option -f "C:\blah\torrc"
or
> tor -install -option -f "C:\blah\torrc"

The "Path to executable:" of "Tor Win32 Service Properties" in Services.msc is
"c:\pathoftor\tor.exe" --nt-service
without parameter instead of
"c:\pathoftor\tor.exe" --nt-service "-f" "C:\blah\torrc" discussed in
that archived post. The "-option -f" parameter is just ignored.




On Tue, Sep 20, 2011 at 1:47 AM, Justin Aplin <japlin@xxxxxxxxx> wrote:
>
> Windows uses a special account, with it's own home directory and separate set of environmental variables, to run NT services. Odds are, when you start the service, tor has no idea where your torrc is, and is dropping to "reasonable default" values. This is why the default ORPort of 9050 is being used.
>
> The trick is declaring a path to the torrc you want to use in the service invocation (using the -f flag), making sure the SERVICE account has permission to read the torrc (which could be an issue if it's in one of your personal home folders), and making sure DataDirectory is declared in your torrc (to ensure the same keys are being used every time).
>
> This is covered in a bit more detail in this archive thread: https://lists.torproject.org/pipermail/tor-relays/2010-June/000381.html
>
> ~Justin Aplin
>
> _______________________________________________
> tor-talk mailing list
> tor-talk@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>
_______________________________________________
tor-talk mailing list
tor-talk@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk