cupsaddsmb appears to disregard the backend information supplied in smb.conf. Specifically, if I use a non-smbpasswd backend (such as LDAP), I get the following trail of errors in the smbd log:
[2003/01/27 14:24:14, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(189) startsmbfilepwent_internal: unable to open file /etc/samba/smbpasswd. Error was No such file or directory [2003/01/27 14:24:14, 0] passdb/pdb_smbpasswd.c:smbpasswd_getsampwnam(1351) unable to open passdb database. [2003/01/27 14:24:14, 1] smbd/service.c:make_connection_snum(681) workst1 (127.0.0.1) connect to service print$ initially as user ADMIN (uid=10012, gid=10000) (pid 504) [2003/01/27 14:24:14, 1] smbd/service.c:close_cnum(859) workst1 (127.0.0.1) closed connection to service print$ Cheers, Waider. -- [EMAIL PROTECTED] / Yes, it /is/ very personal of me. "It's a horrible thing to watch, almost like watching an infant tottering toward a porcupine." - Kyle Jones on MIS people writing C
