samba - May 2006 - lock file information

Does samba store information on lock files in a tdb somewhere? If we
have a process that has a lock on a file that we can't get samba to
surrender, is there a recommended way of forcing samba to release it?
For example, a process on machine A has file B on server X open an
locked.. and the machine A hangs for some reason never releasing the
lock on file B. Is there a recommended way to tell samba its okay to
release any lock on it?

-- 
David Bear
phone: 	480-965-8257
fax: 	480-965-9189
College of Public Programs/ASU
Wilson Hall 232
Tempe, AZ 85287-0803
 "Beware the IP portfolio, everyone will be suspect of trespassing"

On Tue, May 09, 2006 at 02:59:27PM -0700, David Bear
wrote:
> Does samba store information on lock files in a tdb somewhere? If we
> have a process that has a lock on a file that we can't get samba to
> surrender, is there a recommended way of forcing samba to release it?
> For example, a process on machine A has file B on server X open an
> locked.. and the machine A hangs for some reason never releasing the
> lock on file B. Is there a recommended way to tell samba its okay to
> release any lock on it?
The open file database is self-cleaning (killing the smbd process
holding the entry - NOT VIA kill -9, but normal kill) will cause
the next opener to clean out the old entry. The file lock database
(byte range locks) currently is not (it used to be until we ran
into a resource issue with fcntl locks on Solaris). I've committed
a fix to make it self-cleaning again for 3.0.23.

Jeremy.