On Thu, Mar 31, 2011 at 11:55:22AM +0100, Geoff Down wrote:
the most recent times I have tried to restart Tor after a 'killall -INT' I have been presented with the following error: "[warn] Could not bind to 0.0.0.0:9001: Address already in use. Is Tor already running?"
Update: after running those commands, Tor was able to start. Why the delay? Is this normal?
By default Tor takes 30 seconds before it really exits, you can modify this "timeout" by specifying ShutdownWaitLength in your torrc.
Yes, this was after the 30 second wait and tor disappearing from a list of running processes - but thank you both anyway.
A mystery. My guess is either there's something special about your OS X version, or you're doing it wrong. :)
One approach to debugging further might be to use Tor's PidFile option. Tor will create a file when it starts, and remove the file when it exits cleanly.
You might like Debian's init script for examples of starting and stopping Tor: https://gitweb.torproject.org/debian/tor.git/blob_plain/master:/debian/tor.i...
See e.g. check_torpiddir() and wait_for_deaddaemon().
Hope that helps, --Roger