samba - Jul 2004 - pam_smbpass: Cannot access samba password database

I think pam_smbpass it is not initializing all the parameters from smb.conf.

This exhibits itself as "Cannot access samba password database"
messages
in the syslog.  I ran my test code using "truss" and there are
some interesting open() calls:
---------------------------------------------------------------------
20247:  open64("/secrets.tdb", O_RDWR|O_CREAT, 0600)    = 3
20247:  open64("", O_WRONLY|O_APPEND|O_CREAT, 0644)     Err#2 ENOENT
20247:  open64("", O_WRONLY|O_APPEND|O_CREAT, 0644)     Err#2 ENOENT
---------------------------------------------------------------------
I _know_ that my private directory is not set to "/".  And what are
those attempts to open ""?

This is Samba 3.0.4 built on Solaris 9 using gcc 3.2.3 with:
./configure \
         --prefix=/opt/ulcmit \
         --sysconfdir=/etc/ulcmit \
         --localstatedir=/var/ulcmit \
         --with-configdir=/etc/ulcmit/samba \
         --with-privatedir=/var/ulcmit/samba/private \
         --with-lockdir=/var/ulcmit/samba/locks \
         --with-piddir=/var/ulcmit/samba/locks \
         --with-logfilebase=/var/ulcmit/samba/log \
         --without-readline \
         --with-ldap \
         --with-acl-support \
         --with-quotas \
         --with-utmp \
         --enable-cups \
         --without-winbind \
         --with-pam_smbpass \
         --with-ldapsam

I tried setting the PAM argument smbconf=... to a file that
explicitly sets the private directory and it still tries to
open "/secrets.tdb" and "".

Anyone know how to get pam_smbpass to use the right parameters?

-- 
Gary Algier, WB2FWZ          gaa at ulticom.com             +1 856 787 2758
Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054      Fax:+1 856 866 2033

Nielsen's First Law of Computer Manuals:
     People don't read documentation voluntarily.