William A. Rowe, Jr. wrote: > Rainer Jung wrote: >> >> Could be, that there's something wrong with the code that copies the >> listen sockets from the main process to the child. > > Exactly; one of the primary possibilities is that a well documented API, > WSADuplicateSocket does not behave for a given socket provider.
It's also possible that there is an [un]obvious bug. I hate this particular tracing, but I'm off to check this out from the parent/child this afternoon. Yes - my own testing initially has been -X - it explains our discrepancy.
