On Sun, Jul 01, 2012 at 06:14:19AM +0200, Christian wrote:
Really, no logs are created, independent of the logging options.
That's expected -- it's because logs are parsed in the same step as binding the sockets, and it never gets to the 'setting up the logs' part.
The socket unlink issue happens since I use tor and that's for a while now - it never affected functionality.
Who owns that socket file?
The torrc (complete to prevent me from confusing, but slightly spoiled by my mail client with line breaks - RunAsDeamon is set by another default config file):
Anything else in that other default config file?
ORPort 443 NoListen ORPort 0.0.0.0:9090 NoAdvertise ORPort [::]:9090 IPv6Only NoAdvertise
Is this ipv6 bind attempt the one causing problems?
--Roger