check for conflicting *Port directives

Robert Hogan robert at
Sat Jun 23 19:45:04 UTC 2007

if someone does something like:

ORPort 9031
SocksPort 9031

this will tell them where they've screwed up, rather than attempting to bind 
to the port and fail for the second of the two options.

possibly a case of sledgehammer meets walnut (it's a large patch for what it's 
fixing). If the idea is right it will need some cleaning to be up to 
standard, but hopefully this will be less than the time required to write 
from scratch.


Browse Anonymously Anywhere	-
TorK	- KDE Anonymity Manager	-
KlamAV	- KDE Anti-Virus 	-

-------------- next part --------------
A non-text attachment was scrubbed...
Name: conflicting.patch
Type: text/x-diff
Size: 4045 bytes
Desc: not available
URL: <>

More information about the tor-dev mailing list