If you run smbpasswd -a with either the smbpasswd or tdbsam backend and the smbpasswd or passdb.tdb file does not exist, the user gets a confusing error message. This is at debug level 0. tpot@proforma:~/work/samba-pp/samba-3.0/source$ sudo bin/smbpasswd -a tpot New SMB password: Retype new SMB password: pdb_getsampwnam: Unable to open TDB passwd (/home/tpot/work/samba-pp/prefix/private/passdb.tdb)! Added user tpot. tpot@proforma:~/work/samba-pp/samba-3.0/source$ sudo bin/smbpasswd -a tpot New SMB password: Retype new SMB password: startsmbfilepwent_internal: unable to open file /home/tpot/work/samba-pp/prefix/private/smbpasswd. Error was No such file or directory Unable to open passdb database. startsmbfilepwent_internal: unable to open file /home/tpot/work/samba-pp/prefix/private/smbpasswd. Error was No such file or directory Added user tpot. This is pretty awful from a usability point of view. Who cares whether the backend files exist or not? They should be created silently. This is probably not worth worrying about for beta2.
Fixed now. The only small issue regards to tdb backend, but I need to talk to tridge on how to resolve it.
originally reported against 3.0.0beta1. CLeaning out non-production release versions.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.