-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 k.c. chao wrote: > Micah Cowan wrote: > > Have you reproduced this, or is this in theory? If the latter, what has > > led you to this conclusion? I don't see anything in the code that would > > cause this behavior. > > I reproduce this. But I can't make sure the really problem is in > "resolve_bind_address." In the attached message, both > api.yougotphogo.com and farm1.static.flickr.com get the same > ip(74.124.203.218). The two wget are called from two threads of a > program.
Yeah, I get 68.142.213.135 for the flickr.com address, currently. The thing is, though, those two threads should be running wgets under separate processes (I'm not sure how they couldn't be, but if they somehow weren't that would be using Wget other than how it was designed to be used). This problem sounds much more like an issue with the OS's API than an issue with Wget, to me. But we'd still want to work around it if it were feasible. What operating system are you running? Vista? - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer, and GNU Wget Project Maintainer. http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIirT17M8hyUobTrERAjsuAJ0crMPYIQficu1csou8Tt0jDFKvpQCeNYk3 1FhXl3uUYj2IA53qI1oOJ8A= =DvdG -----END PGP SIGNATURE-----
