On 02/22/2013 03:12 PM, Nathan Scott wrote:
Hi Dave,
----- Original Message -----
This is good news Nathan. It looks to me like most of the failures
could
potentially be due to the same ipv6 socket leak. I may be able to
track
it down before you wake up. It's Saturday for you now anyway, so no
need
for you to delve into it unnecessarily.
Thanks. I don't think its a leak, I think its just there now where
it wasn't before (an extra fd, and open port) - the extra log file
diagnostics, netstat output is showing another port, etc.
Yeah, I figured that out while working on 172.
Oh, except for 197, not sure what that is yet.
Me neither. I looked into it, but got nowhere. While the fds do not
appear to be leaking through the exec() call, there do seem to be more
of them after pmNewContext() is called. The results are identical for
NSS and non-NSS builds.
I merge from you dev branch again and added my updates on top of that
into brolley/nssmerge. Included in today's updates are a fix for qa/172
and code to complete the non-NSS implementation of IPv6 support in libpcp.
Dave
|