On Monday 20 April 2009 23:48:47 Tim Judd wrote: > > 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)
As far as I know, named never supported or needed xml. I would check if this really is named and for rootkits while you're at it. Either that, or you have LDFLAGS set in your /etc/make.conf that make everything link with these libraries. Backup data and configs and reinstall from CD if you can't find a sane answer for this. > libm.so.2, in /usr/local/lib/compat/libm.so.2 is for Linux (and might I > add a possibly older version). No, it's from compat4x. Linux would be in /compat/linux/lib. -- Mel _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"