Re: Can't get named_sdb to load postgres modules?

On Tue, May 12, 2009 at 2:18 PM, Todd Lyons <[email protected]> wrote:
>
> You mentioned about debug output saying that it was loading the SDB
> modules. If you check the named_sdb binary and see dynamic links to
> mysql, ldap, and postgres libs, I think we can say that your binary
> has the proper support, but the debug output is authoritative.  Mine

Forgot to paste this, but these are the dynamic linkings mine has to
give you a reference.  You can see it's linked against mysql, ldap,
sqlite, and postgres (libpq), as well as sasl.  If yours is not
dynamically linked to those, then I cannot see how it will work
(unless it's statically compiled, but without seeing how it's built,
no real way to tell).

CentOS52[root@ivdns51 ~]# ldd /usr/sbin/named-sdb
	liblwres.so.40 => /usr/lib64/liblwres.so.40 (0x00002ac6a6dfb000)
	libdns.so.43 => /usr/lib64/libdns.so.43 (0x00002ac6a700c000)
	libbind9.so.40 => /usr/lib64/libbind9.so.40 (0x00002ac6a7354000)
	libisccfg.so.40 => /usr/lib64/libisccfg.so.40 (0x00002ac6a755f000)
	libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00002ac6a777b000)
	libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00002ac6a79a9000)
	libisccc.so.40 => /usr/lib64/libisccc.so.40 (0x00002ac6a7cf2000)
	libisc.so.41 => /usr/lib64/libisc.so.41 (0x00002ac6a7ef9000)
	libmysqlclient.so.15 => /usr/lib64/mysql/libmysqlclient.so.15
(0x00002ac6a8145000)
	libz.so.1 => /usr/lib64/libz.so.1 (0x00002ac6a84b8000)
	libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00002ac6a86cc000)
	libm.so.6 => /lib64/libm.so.6 (0x00002ac6a8904000)
	libodbc.so.1 => /usr/lib64/libodbc.so.1 (0x00002ac6a8b88000)
	libldap-2.3.so.0 => /usr/lib64/libldap-2.3.so.0 (0x00002ac6a8dec000)
	liblber-2.3.so.0 => /usr/lib64/liblber-2.3.so.0 (0x00002ac6a9026000)
	libpq.so.4 => /usr/lib64/libpq.so.4 (0x00002ac6a9235000)
	libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 (0x00002ac6a9457000)
	libcap.so.1 => /lib64/libcap.so.1 (0x00002ac6a96b1000)
	libnsl.so.1 => /lib64/libnsl.so.1 (0x00002ac6a98b6000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ac6a9ace000)
	libc.so.6 => /lib64/libc.so.6 (0x00002ac6a9ce8000)
	libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00002ac6aa03d000)
	libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00002ac6aa2d0000)
	libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00002ac6aa4f5000)
	libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00002ac6aa6f8000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00002ac6aa900000)
	libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00002ac6aab04000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00002ac6aad07000)
	libssl.so.6 => /lib64/libssl.so.6 (0x00002ac6aaf1c000)
	libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00002ac6ab166000)
	/lib64/ld-linux-x86-64.so.2 (0x00002ac6a6bdf000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x00002ac6ab37f000)
	libsepol.so.1 => /lib64/libsepol.so.1 (0x00002ac6ab598000)

I tend to think you would get a lot more variables answered/known if
you would grab the atkac src.rpm for 9.5.x, build it, and install it.
If you have time to test, it wouldn't be wasted time.
-- 
Regards...      Todd

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com