named fails to start on boot on FreeBSD 6.1, complains about libxml2.so.5

[Tim Judd]

On Mon, Apr 20, 2009 at 2:20 PM, Mark Stosberg <mark at summersault.com> wrote:

>
> We had problem with "named" starting on boot on a FreeBSD 6.1 server,
> managed
> by /etc/rc.conf.
>
> The startup script failed with errors about shared library "libm.so.2"
> failing
> to load because of something related to libxml2.so.5.
>
> Later, when I then tried starting it via /etc/rc.d/named it worked fine.
>
> I include the following "ldd" output in case it's helpful. What could
> possibly
> be the issue here?
>
>    Mark
>
> ###
>
> # ldd /usr/sbin/named
> /usr/sbin/named:
>        libcrypto.so.4 => /lib/libcrypto.so.4 (0x281ff000)
>        libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x282f1000)
>        libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x283ef000)
>        libm.so.4 => /lib/libm.so.4 (0x284e3000)
>        libc.so.6 => /lib/libc.so.6 (0x284f9000)
>        libm.so.2 => /usr/local/lib/compat/libm.so.2 (0x285d1000)
>
>
I see it has the linux libm as a shared library...  shouldn't happen when
it's freebsd's named binary.


libm.sp.4, in /lib/libm.so.4    is for BSD
libm.so.2, in /usr/local/lib/compat/libm.so.2     is for Linux (and might I
add a possibly older version).