smbpasswd database is corrupt error

[Tim Winders]

Fortunately I was able to figure out the problem pretty quickly.  The log
file claims the password database is corrupt (which is really isn't) and
then says that user xxx can't be found in the unix passwd database, so I
was able to remove those users from the smbpasswd file and that fixed my
immediate problem.  I can live with it, I just wanted to make sure it was
logged as a problem.  Besides, if I didn't want to bleed, I wouldn't be
using the HEAD branch!  <hehe>  If it gets to crazy, I can get the beta1
code pulled down and installed pretty quickly.

Thanks for the response!

=== Tim

---------------------------------------------------------------------
|  Tim Winders, CNE, MCSE     |  Email:  Tim.Winders at SPC.cc.tx.us   |
|  Network Administrator      |  Phone:  806-894-9611 x 2369        |
|  South Plains College       |  Fax:    806-897-4711               |
|  Levelland, TX  79336       |                                     |
---------------------------------------------------------------------


On Wed, 18 Nov 1998, Jeremy Allison wrote:

> Tim Winders wrote:
> > 
> > OK.  I am using the cvs HEAD from this morning and I found a problem with
> > the way smbd deals with the smbpasswd database.  If a username is in the
> > smbpasswd file but *NOT* in the unix passwd file it reports an error that
> > the smbpasswd database is corrupt and will not let the user login.  I
> > *THINK* this only occurs to users listed AFTER the "problem" in the
> > smbpasswd file.  I don't think previous alpha versions worked the same
> > way.
> > 
> 
> Yes, I'm afraid Luke's latest changes have broken the HEAD
> branch quite a bit. Unfortunately I have logged the problems
> and sent them to him but he added so much new code (and re-arranged
> so much) that with preparing for the 2.0 release I haven't had time
> to go through and understand what he broke (although I fixed the
> gross compile errors).
> 
> I wish he hadn't added a new load of code just before going 
> off to a conference, that was not best way to keep the code
> stable.
> 
> Let me know if it's unbearable and I'll revert his change
> and he'll have to re-add it when he gets back and has
> some time to clean up the mess himself :-).
> 
> Jeremy.
> 
> -- 
> --------------------------------------------------------
> Buying an operating system without source is like buying
> a self-assembly Space Shuttle with no instructions.
> --------------------------------------------------------
>