Using Mandrake samba-2.2.8a-13mdk: The connections, locking and brlock tdb in the /var/cache/samba directory have to be manually deleted after a samba shutdown. Then samba has to be started, (creates the .tdb's), shutdown because it appears that smbstatus gives a locking error, and then restarted. Reading other messages on the newsgroup it appears that these databases should be automatically cleared on a restart.
Cleared on first use is more appropriate description. Has a new connection been received since you restarted?
After working with this for awhile, it also appears that a NT 4 server could have something to do with this. I am working with a database application that uses foxpro databases. There are many clients during the day that open the databases (over 50) for use with the client OS being Win95, Win98, WinME, Win2K and WinXP. There is one machine that is WinNT4 (with all the patches) which is used as our batching machine. Once in awhile we have to kick everone out of the program to do maintenance or enhancements. After a smbstatus shows there are currently no open files or locks, we try to open a database exclusively with no success from any of the clients except the WinNT4 machine. A samba restart does not even clear the locks.
Sorry, but the 2.2 is not under development any longer. If you can reproduce this bug against the latest 3.0 release, please reopen this bug and change the version in the report. Thanks.
database cleanup