Matt Sergeant wrote: > May be a problem with forking. Here's part of the fork replacement I use > in my code that uses the single-packet-DNS stuff:
Justin's code generates a number from the pid to initialize the ID counter and keeps track of it itself instead of relying on the Net::DNS code. Are there some systems in which fork does not result in a new pid? Is it the case that the socket created in each process would use a different source port on the local host? I don't see how there can be so many collisions without both the pid and the source port being the same. -- sidney
