samba - Apr 2005 - File locks db (manually removing locks)

After killing an smbd process, or occasionally after a process has died
itself, there remains a lock as indicated in an smbstatus output.

The process ID tied to the file lock in the db is no longer active, yet the
db entry still exists. Is there a way to manually manipulate the file locks
db? If not, will any of these entries prohibit another smbd process from
handling the file which is indicated as locked? Or will a new process simply
validate the running/not running status of the process id indicated in the
db before proceeding itself?

On a side note, is there any detailed documentation as towards the various
db files shared by the smbd processed? Something more detailed than your
typical how-to in regards to why and what they do, vs. actually reading
through the source code or something? Just some reading I wouldn't mind
taking the time to do; the more I can familiarize myself with the internals
of samba, the better admin I may become :)


--
Nathan Vidican
nvidican@wmptl.com
Windsor Match Plate & Tool Ltd.
http://www.wmplt.com/

On Wed, Apr 06, 2005 at 07:53:32AM -0400, Nathan Vidican
wrote:
> After killing an smbd process, or occasionally after a process has died
> itself, there remains a lock as indicated in an smbstatus output.
> 
> The process ID tied to the file lock in the db is no longer active, yet the
> db entry still exists. Is there a way to manually manipulate the file locks
> db? If not, will any of these entries prohibit another smbd process from
> handling the file which is indicated as locked? Or will a new process
simply
> validate the running/not running status of the process id indicated in the
> db before proceeding itself?
Yes, that's what the smbd's do when finding an existing lock entry. They
send a kill 0 signal to the process to validate its existence.

Jeremy.