On Thu, 4 Oct 2007, Dan Fandrich wrote:

> The fix for this went in with the comment "I wrote a test case (1009) to
> verify this, but it is a bit error-prone since it will have to pick a fixed
> local port number and since the tests are run on so many different hosts in
> different situations I add it in disabled state." While it's a legitimate
> concern that the port might be in use by something else, it's not an
> unprecedented situation; test cases 19, 504, 702-705 already rely on certain
> ports being unoccupied. While there could be sporadic failures because of
> this, I wouldn't worry about it too much--the existing sporadic (the SSH
> authentication issue) and persistent (Mac OS X, IRIX) failures should be
> tackled first!

Yeah, it also struck me that I should probably set it with a reasonably wide
range like 44444-448000 or whatever, which should make failures unlikely.

I'll modify and remove it from disable...

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html