Tor doesn't find any dns server address and dies.
I am using Tor on Debian Etch. By default the daemon is configured to start in runlevel 2 with S20tor. When the system starts, there is a race condition of the daemons on the same run-level and if the daemon which is responsible to update resolv.conf hasn't yet updated the file with the right dns ip addresses- this is probably due to delay in polling the router for nameservers address and to race conditions, tor dies. At the moment I don't remember the name of the program which is responsible to update the above-mentioned file.
This is very annoying,because I often start the system and then I don't find the expected instance of tor running, even if the resolv.conf is always correctly updated For me it's better if the started instance of tor,keep polling the resolv.conf file at some rate, and then after say 20 times,it dies.
Also moving the name of the file to something like S50tor seems to help partially as the problem seems just to slightly decrease.(this confirm the race condition problem)
I attach the log output. Output of tor --version: Tor version 0.2.0.31 (r16744).
Log:Dec 08 14:30:35.125 [notice] Tor 0.2.0.31 (r16744) opening log file. Dec 08 14:30:35.168 [warn] eventdns: Unable to add nameserver 126.96.36.199: error 2 Dec 08 14:30:35.169 [warn] eventdns: Unable to add nameserver 188.8.131.52: error 2 Dec 08 14:30:35.169 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (6) Dec 08 14:30:35.169 [err] Error initializing dns subsystem; exiting
[Automatically added by flyspray2trac: Operating System: Other Linux]