When configuring OR/Dir Ports, Tor always processes OR Port change first
I wasn't exactly sure how to phrase the subject, so feel free to rename it.
Basically, when you change the OR or Directory Port Settings in Vidalia, Tor will always try to configure the OR Port first.
This creates a problem if the user tries to switch the OR Port and the Dir Port (or just change the OR Port to the current Dir Port, and change the Dir Port to anything else). In short, in such a scenario, Tor blocks itself.
For example: Say a Tor Server was configured to use Dir Port 443 and OR Port 8080. If the user tried to change it to use Dir Port 80 and OR Port 443, the following error message would be presented:
[Warning] Could not bind to 0.0.0.0:443: Address already in use [WSAEADDRINUSE ]. Is Tor already running?
This error message would be presented because Tor first closes the OR Port, 8080. It then tries to open Port 443, but it is already using Port 443 as the Dir Port.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]