Maintained by: NLnet Labs

[Unbound-users] unbound daemon linking bug?

W.C.A. Wijngaards
Tue Oct 11 17:11:18 CEST 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/11/2011 04:54 PM, Paul Wouters wrote:
> On Mon, 10 Oct 2011, Matthijs Mekking wrote:
> 
>>>> I don't fully grasp your problem: if unbound does not link against
>>>> libunbound, upgrading the unbound package would not need to update the
>>>> libunbound package.
>>>
>>> But if a fix is applied to unbound-libs, the unbound daemon will still
>>> be using an old copy. Also, the results of unbound vs unbound-host could
>>> then be different.
>>
>> Seems to me that this is a thing that the package maintainer should
>> maintain.
> 
>> Dynamic linking *may* increase paging thus decreasing performance.
> 
> The package maintainer thinks upstream should reconsider their view, or
> perhaps back these up with actual numbers instead of hypothesis :)

Yes I do not think this is a big issue.  Dynamic linking and chroot
feature (on not wonderfully packaged environments) can be painful.

>> - --enable-allsymbols is indeed what you want.
> 
> I tested this, and it works indeed. I'll add it to the new releases
> of unbound. Thanks!

Note that this means libunbound exports internal symbols, not just the
'libunbound API'.  Those symbols 'pollute' the linking environment of
the user program, i.e. conflict if they also use dns_cache_store() and
so on.

This is why the option is not enabled by default.  We could get around
this by having libunbound-internal and libunbound (that links to
libunbound-internal again).  And so on, but it gets more complicated,
static binaries can be very nice for system critical services in some
situations, so this option we have to also keep around...

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOlFyWAAoJEJ9vHC1+BF+NaacP/3Go9y3UfWswlMzItyoc5qlk
xAxYTAWM/jqkjKF4WIRSVg2lwHXbma9Wf4mICkMvLR68oZe/lG2Gp9RvLmjkwEPX
iALNWgox26UqIeEbYf+Ji0m1pK8+glsgYZMl+YDmwJ1fRcIuwGzmfDl5PwPCKGxx
MKLWug/+pEgUhCaF7EjZ9AURA1vO7af3LIGaPGrxpQbyybnYkHo+FGoyZmH7IOoL
AHWBXwGhgHIiSdNezvorV6Rf1F909YePcABIDzI01VDSQw3evQ7QKSgS/Rt5sj/j
i/uJJZo+SsW9wPPNSBnsL8zTP6DRPpEifpk6cWe2ZoZCYSpeg2foIUyoCh0YYjeM
EgEKC5v8Is825NL4IykPHk6qmnz21XLNiYsUNQQ8eRLRgJQxbZLJGO0tYCqCQYbm
nZqU0Ia+AWBn6x6a9412Fhbzq+w2cpULbN63PCA5gDn2FoOWGAdxxSOTkIvFYEpr
RQeMTCxLQor6/KS7/3qZEwIb2Ng0APIgKtYD9+SWnBm+2ql9jCZ3cXO9okkUE20L
PBuHl1p6tkwt3+m7wTpatUvx4wXalJrBdQuXUukFJTdgvCcI7eI7u0YFuie0F/h+
NK2AxmwWHz6H5xU8MhhUouap7aNRS/MOc4hUfiSiYp8/wigOURkJ8dMLLOOuzKb8
s9TngCTJqLQmPbT3CMD6
=Z+gL
-----END PGP SIGNATURE-----