torr file question...

[Aplin, Justin M]

Simply edit the torrc while both Tor and Vidalia are closed. Vidalia 
edits the torrc file when changes are made using its interface; upon 
starting up, however, I believe it gathers its parameters directly from 
the torrc. In my experience when I write a custom torrc with Tor and 
Vidalia closed, and then start Vidalia (which in turns starts Tor), my 
custom torrc is overwritten, but upon careful observation of the new 
file, it can be seen that each of my settings remains the same, although 
reordered and with added header comments.

I do wish there was a "do not edit torrc" or "confirm before editing 
torrc" option in Vidalia, but generally the changes it makes are 
harmless. C'est la vie.

~Justin Aplin



On 2/3/2011 4:56 PM, Zaher F. wrote:
> i am usingVidalia Bundle 0.2.1.29-0.2.10
>
>
> and i found in my torcc file this :
>
>
>
> This file was generated by Tor; if you edit it, comments will not be 
> preserved
> # The old torrc file was renamed to torrc.orig.1 or similar, and Tor 
> will ignore it
>
> # If set, Tor will accept connections from the same machine (localhost 
> only)
> # on this port, and allow those connections to control the Tor process 
> using
> # the Tor Control Protocol (described in control-spec.txt).
> ControlPort 9051
> # Where to send logging messages. Format is minSeverity[-maxSeverity]
> # (stderr|stdout|syslog|file FILENAME).
> Log notice stdout
> # Bind to this address to listen to connections from SOCKS-speaking
> # applications.
> SocksListenAddress 127.0.0.1
>
>
>
>
> so how i can control and  fix or define my exitnode????
>
>
> thx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-talk/attachments/20110203/d2b5ad11/attachment.htm>