Jeroen, Jeroen Besse wrote: > Hi, > > Sorry, please disregard this thread. My system probably needed the > monthly reboot... ;-) (works now)
You were probably a victim of an OS/2 TCP/IP bug with the HOSTS file handling. From what I recall, one of two things happen (can't remember which one) : - the HOSTS file gets opened and parsed only at the time the application initializes TCP/IP. If you modify it while an application is already running, it will not have any effect. - names are only resolved from the HOSTS file the first time around, and after that they are cached. So if it was a miss the first time because it was missing from the HOSTS file at the time, it will always go to the DNS afterwards, until you close the application Either way, it's not nice behavior. The OS/2 TCP/IP stack should be able to detect that the HOSTS file has been modified and reread it while the application is running. It should do that during lookups. Unfortunately, I don't know where to post this bug for IBM to fix. I posted it in comp.os.os2.bugs about 5 years ago, and it didn't get fixed ... -- "Except for the lack of debugging and the ps thing, [Linux] kernel threads are generally fine right now. And if you're not too fussed about the more fiddly details of POSIX threads, and your application doesn't spend most of its time in thread creation, then LinuxThreads is great too." Linux-Kernel archive
