Quoting David Anselmi (anse...@anselmi.us): > Package: samba > Version: 2:3.4.2-1 > Severity: normal > > When upgrading a domain controller from 2:3.3.4-1 -> 2:3.4.2-1 my domain > became > unusable because the user/machine accounts were lost. > > Running pdbedit -L showed none of my Windows accounts (just the accounts from > the Linux server). > > Fortunately /etc/samba/smbpasswd still contained the accounts so: > > sudo pdbedit -i smbpasswd:/etc/samba/smbpasswd -e > tdbsam:/var/lib/samba/passdb.tdb > > seems to have recovered. > > Running: > > testparm -s --parameter-name "passdb backend" 2>/dev/null > > shows tdbsam but there has been no change to smb.conf to cause that to be > different now.
The default setting of "passdb backend" changed from "smbpasswd" to "tdbsam" in samba 3.4.0 The default configuration file we provide in Debian has an explicit definition of "passdb backend = tdbsam" since the Lenny release cycle. So, people who use our default configuration will not be harmed by this default setting change. Only people who have *no* setting ofr "passdb backend" will suffer from the same problem you had. Steve, as you upgraded this bug to RC, I guess you somehow mean that we should do something. Last (and only time) we talked about this (June 25th), the conclusion was to mention something in NEWS.Debian. A stronger solution would be running a test to check whether "passdbbackend" is defined in smb.conf and warn the local admin if it is not (and if this is an upgrade from a pre-3.4.0 version). Comments?
signature.asc
Description: Digital signature
