Hi list,
I'm having some trouble getting saslpasswd2 to work. I am running
OpenPKG-CURRENT (20050314) on SunOS 5.9 (sun4u).
Anytime I run saslpasswd2 (as root) to create new user credentials, it
fails with a "generic failure". I've truss-ed the process and noticed
that after saslpasswd2 stats and opens /openpkg/lib/sasl/libsasldb.so
it starts to stat all kinds of places, looking for libdb-4.2
stat("/usr/lib/libresolv.so.2", 0xFFBFD154) = 0
stat("/usr/lib/libsocket.so.1", 0xFFBFD154) = 0
stat("/usr/lib/libnsl.so.1", 0xFFBFD154) = 0
stat("/usr/lib/librt.so.1", 0xFFBFD154) = 0
stat("/usr/lib/libdb-4.2.so", 0xFFBFD154) Err#2 ENOENT
stat("/usr/local/lib/sasl2//libdb-4.2.so", 0xFFBFD154) Err#2 ENOENT
stat("/usr/local/lib/libdb-4.2.so", 0xFFBFD154) = 0
There is however not open call for any of these files. Afterwards, the
libsasldb init functions are successfully called.
-> libsasldb:_init(0x0, 0x0, 0xff3f7594, 0x2df08)
<- libsasldb:_init() = 0
-> libsasldb:sasl_auxprop_plug_init(0x58dc0, 0x4, 0xffbfd8cc, 0xffbfd8c8)
-> libsasldb:sasldb_auxprop_plug_init(0x58dc0, 0x4, 0xffbfd8cc, 0xffbfd8c8)
<- libsasldb:sasl_auxprop_plug_init() = 0
LDD-ing saslpasswd2 gives me
# ldd /openpkg/sbin/saslpasswd2
libresolv.so.2 => /lib/libresolv.so.2
libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
librt.so.1 => /lib/librt.so.1
libdl.so.1 => /lib/libdl.so.1
libdb-4.2.so => /usr/local/lib/libdb-4.2.so
libc.so.1 => /lib/libc.so.1
libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
libmp.so.2 => /lib/libmp.so.2
libaio.so.1 => /lib/libaio.so.1
libmd5.so.1 => /lib/libmd5.so.1
/usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
/usr/platform/SUNW,Ultra-60/lib/libmd5_psr.so.1
which I find strange, since LD_LIBRARY_PATH is set to
# echo
/openpkg/lib:/openpkg/local/lib:/usr/local/lib:/usr/local/ssl/lib:/opt/swf/lib:/lib:/usr/lib
Is this a problem with my config (having a parallel installation of
Berkeley DB), or is ther a problem with the -current source rpm? I'm
assuming, that the error stems from the fact, that sasl is using DSOs
from outside openpkg. Shouldn't it be statically linked?
Any hints or suggestions on what else might be wrong or how to fix
this are greatly appreciated.
-- Olaf Mersmann
P.S: If needed, I can post the full truss log here and/or eMail it to
someone off list for futher analysis..
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List openpkg-users@openpkg.org
