On October 19, 2013 11:51:14 AM Ivo De Decker wrote: > Hi Steve, > > Thanks for all the info. That really helps!
Thank YOU (the Samba Team) for diligent analysis of bug reports! It can't be easy on a complex configurable suite like Samba. > It's not immediately clear why /var/lib/samba/private/passdb.tdb existed, > but this issue reminds me of #454770. I guess you track unstable on this > system? Yes, I track unstable and tend to do updates every few days so if ever there was a bug introduced in one revision and fixed in the next ... it's likely I got bitten :-) > The best thing I can propose, is to fail on upgrade when both files exist, > so that the admin has to do the cleanup manually. There isn't really a good > way for a script to decide which file is the right one. At least the admin > will know that something is going wrong, instead of silently getting old > (possibly empty) user data. I would support this kind of approach! > > > - do you have backups from before the upgrade? Could you get the > > > contents of> > > > > smb.conf and the directory listings mentioned above from before the > > > upgrade?> > > Yes, I have backups. I'll recover them and send in a separate email. > > It seems the smb.conf didn't change. No. I got the usual "file has changed, look at the diffs, take the new, etc" dialog. I chose to keep the existing. Then I looked at the new config file and didn't see anything worth changing. > Also, you weren't using smbpasswd. You old smbpasswd was converted to > passdb.tdb during an uprade years ago. Good to know. I will remove /etc/samba/smbpasswd, then. Thanks, -Steve
signature.asc
Description: This is a digitally signed message part.