I'd been wondering why a couple of things on our new Linux image weren't working quite right.
When students went to log into their lockers (hosted on a Samba share), it prompted them for their Username, Domain, and Password and the Domain was filled in as "WORKGROUP". I figured this was rather strange, since it showed up as "MCCSC" on the old image, what it should be.
"Oh well," I concluded, "I've got too many things coming at me to worry about this little thing, the students can type 5 extra characters when they want to get to their lockers, it's no big deal..."
I'm starting to wonder now whether it's not just the symptom of a much more basic problem.
The thing that got me to re-evaluate my conclusion was the fact that on the new image, WINS resolution just isn't working. After conversing with my friend, Google, and consulting my other friend, Book, I stared at the configuration file that I had DEFINITELY set correctly. I compared it to the configuration file from the old image, the one that works right, and everything was the same, but the new image just wasn't behaving properly.
Although feeling vindicated in that I did not cause the problem, I'm perplexed because that means I can't undo any stupid mistakes and have it fixed. Not to mention, since it's not working right I'm still got a bad feeling that it's my fault.
I ran the "testparm" command which is a very basic diagnostic that just tells you whether /etc/samba/smb.conf is correctly formatted, and *gasp* there's an error...but not in the smb.conf file! I ran "testparm" on the old image and no errors.
These are the three errors I get running "testparm" on the new image:
ERROR: lock directory /var/run/samba does not exist
ERROR: pid directory /var/run/samba does not exist
WARNING: passdb expand explicit = yes is deprecated
The strange thing is that these errors pop up AFTER it already says that it "Loaded services file OK.", so where the hell is it getting "passdb expand explicit = yes" from?!
Still not quite convinced that I didn't break something somehow, I booted to the Ubuntu Live CD, absolutely fresh image, ran testparm and BANG! Same three error messages!
It's NOT my fault! Hooray, I have proof!
Now...what gives? and how do I fix it?
Google is not being helpful at all with these error messages, which is rare.
I wasn't able to flag a live person on #samba on irc.freenode.net. I said the following there:
I am running Ubuntu Edgy Eft (testparm -v = 3.0.22), and I noticed that none of the parameters I was specifying in my smb.conf file seemed to actually be DOING anything. I looked long and hard and consulted online documentation, Google, even a book (Linux in a Windows World), compared my smb.conf to one I had on an earlier installation (Ubuntu Breezy Badger, testparm -v = 3.0.14a-Ubuntu) that was working fine, and came to the conclusion that I had everything correct.
After painstakingly assuring myself that my smb.conf file was correctly formed as I wanted it, I tried "testparm" and noticed that I got three strange error messages AFTER being informed that it "Loaded services file OK.", these were "ERROR: lock directory /var/run/samba does not exist", "ERROR: pid directory /var/run/samba does not exist" and "WARNING: passdb expand explicit = yes is deprecated"
None of these errors are present when I run testparm on Breezy. Anyhow, just to make sure I hadn't made any stupid mistakes along the way I booted to the Ubuntu Live CD, ran testparm, and got the exact same error messages.
What gives? More importantly, how do I fix it?
Any help would be greatly appreciated!
powered by performancing firefox