Date: Tue, 23 Jun 2015 13:09:07 +0200 From: Fabian Keil freebsd-listen@fabiankeil.de
nusenu nusenu@openmailbox.org wrote:
… Did you test with custom flags like "--+Log ${tor_loglevel} file ${tor_logfile}"?
This should read "--Log" no?
While I prefer using neither "--Log" nor "--+Log", the latter is valid syntax and used in the real world: https://svnweb.freebsd.org/ports/head/security/tor-devel/files/tor.in?view=m...
…
- From tor's man page:
Other options can be specified on the command-line in the format "--option value", in the format "option value", or in a configuration file.
Looks like the man page is incomplete.
See the next section, "THE CONFIGURATION FILE FORMAT"
By default, an option on the command line overrides an option found in the configuration file, and an option in a configuration file overrides one in the defaults file. This rule is simple for options that take a single value, but it can become complicated for options that are allowed to occur more than once: if you specify four SOCKSPorts in your configuration file, and one more SOCKSPort on the command line, the option on the command line will replace all of the SOCKSPorts in the configuration file. If this isn't what you want, prefix the option name with a plus sign, and it will be appended to the previous set of options instead. Alternatively, you might want to remove every instance of an option in the configuration file, and not replace it at all: you might want to say on the command line that you want no SOCKSPorts at all. To do that, prefix the option name with a forward slash.
teor
teor2345 at gmail dot com pgp 0xABFED1AC https://gist.github.com/teor2345/d033b8ce0a99adbc89c5
teor at blah dot im OTR D5BE4EC2 255D7585 F3874930 DB130265 7C9EBBC7
tor-relays@lists.torproject.org