@acebmxer said:
@rzr
No issues to report initially other then nslookup still an issue.
openssl_link.c:132: INSIST(dst__memory_pool != ((void *)0)) failed, back trace
Yes I looked at it, it looks like it's a design isssue that was fixed in later version of bind.
In details If I understand correctly this patched version of nslookup is facing a SIGARBT caused by an assert on previously cleanup resources (dst__memory_pool) which is unexpected in finishing part of the openssl thread (dst__openssl_destroy).
This bind version (were ssl support is in progress) is also known to have memory leaks, but those are resolved in later version, so until we catch up you'll probably have to live with this little annoyance on process exit unless we find (and validate) a better fix.
