1 --- tor-0.2.9.10/src/config/torrc.sample.in.~1~ 2017-02-17 19:47:43.000000000 +0300
2 +++ tor-0.2.9.10/src/config/torrc.sample.in 2017-05-02 21:22:37.595049434 +0300
4 ## We advise using "notice" in most cases, since anything more verbose
5 ## may provide sensitive information to an attacker who obtains the logs.
7 -## Send all messages of level 'notice' or higher to @LOCALSTATEDIR@/log/tor/notices.log
8 +## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
9 #Log notice file @LOCALSTATEDIR@/log/tor/notices.log
10 -## Send every possible message to @LOCALSTATEDIR@/log/tor/debug.log
11 -#Log debug file @LOCALSTATEDIR@/log/tor/debug.log
12 +## Send every possible message to /var/log/tor/debug.log
13 +Log debug file @LOCALSTATEDIR@/log/tor/debug.log
14 ## Use the system log instead of Tor's logfiles
17 ## To send all messages to stderr:
20 ## Uncomment this to start the process in the background... or use
21 ## --runasdaemon 1 on the command line. This is ignored on Windows;
22 ## see the FAQ entry if you want Tor to run as an NT service.
26 ## The directory for keeping all the keys/etc. By default, we store
27 ## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
28 -#DataDirectory @LOCALSTATEDIR@/lib/tor
29 +DataDirectory @LOCALSTATEDIR@/lib/tor
31 ## The port on which Tor will listen for local connections from Tor
32 ## controller applications, as documented in control-spec.txt.
34 ## See https://www.torproject.org/docs/tor-doc-relay for details.
36 ## Required: what port to advertise for incoming Tor connections.
39 ## If you want to listen on a port other than the one advertised in
40 ## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
41 ## follows. You'll need to do ipchains or other port forwarding