Hi Steve Steve Langasek wrote: > On Fri, Aug 18, 2006 at 06:14:37PM +0900, Michael Neuffer wrote: >> Peter Eisentraut wrote: >>> Am Freitag, 18. August 2006 10:38 schrieb Michael Neuffer: >>>> passdb backend = tdbsam, > >>> This is your problem. There is no passdb backend named "tdbsam,". You >>> want "tdbsam". Do you have any idea how that comma got in there? Because >>> you're the second person reporting this problem. > >> Yes, the line was once: > >> passdb backend = tdbsam, guest > >> During some upgrade in the dark past the guest must have been dropped >> and the comma remained. Due to this I suspect, that there will be even >> more people who will run into this problem during their next >> upgrades/updates. > >> A solution that I already mentioned to Steve would be to release another >> update to the package that scans for this comma in the preinstal script >> and removes it auto-magical-ly.... > > The thing is that there are many ways that a user might have set their > passdb backend which happened to work, but which were never correct > according to the documented syntax. I'm pretty sure that "backend1, > backend2" was not the documented syntax, and that it was rather always > "backend1 backend2". I don't know why you had that comma there, but in > general I don't think Debian should take responsibility for fixing up user > config files wrt changes in the strictness of implementing the documented > syntax -- only when the approved syntax changes. > > If you can point me to some resource that said to use the comma, then I'll > happily implement that check.
I'm like 99.5% sure that it must have come from swat, which I had used to generate the original version of that config file. Cheers Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
