-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pretty sure this is the case, but does pam_smbpass work with tdbsam as a
backend? We are moving from smbpasswd to tdbsam in an upgrade that is to
take place shortly, and I want to make sure I'm not going to mess things
up.
Thanks for the help! I'm upgrading, incidentally, from 3.0.11 to HP's
CIFS/9000 (I'm going to be compiling pam_smbpass independently -- I've
found that for my purposes that works just fine).
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III
|$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (HP-UX)
iD8DBQFGOgpsmb+gadEcsb4RAiGxAJ4niIDIXPHq8sZ2kCJJI9tQt4ikPgCgnTbs
qC1QcszSkH1Oi11CQ6L6Kz0=
=fPOq
-----END PGP SIGNATURE-----
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
