On 8/21/07, coderman <[EMAIL PROTECTED]> wrote: > ... > yup, same experience here.
i lied! looking back over this i did not set a ORListenAddress. when i changed this and tried to reload the config the server died. i don't know if this is related to the socks listener address change issue, but it sounds similar. i tried reproducing the socks problem but it worked fine with 0.2.0.4-alpha (that is, it correctly closed the old port, and created a new one bound to the new address) i tried the ORListenAddress change and the following occurred: Aug 21 15:41:28.773 [notice] Received reload signal (hup). Reloading config. Aug 21 15:41:28.774 [notice] Closing no-longer-configured OR listener on 0.0.0.0:9001 Aug 21 15:41:28.774 [notice] Opening OR listener on 127.0.0.1:9001 Aug 21 15:41:28.774 [warn] Could not bind to 127.0.0.1:9001: Address already in use. Is Tor already running? Aug 21 15:41:28.774 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Aug 21 15:41:28.774 [err] Reading config failed--see warnings above. For usage, try -h. Aug 21 15:41:28.774 [warn] Restart failed (config error?). Exiting. (in the original case i was rebinding to a public IP; the loopback is just for test, but the same behavior was encountered.) hope that clarifies things. best regards,
