On Tue, Apr 12, 2005 at 08:11:59AM -0400, Nathan Vidican wrote:
> Okay, but then if the process signals back that is in fact not there, why
> then do the locks remain?
No, the smbd process that detected the problem should then remove that entry.
> I killed all smbd processes last night, and
> res
al Message-
From: David McCann [mailto:[EMAIL PROTECTED] On Behalf Of Mac
Sent: Tuesday, April 12, 2005 9:53 AM
To: Nathan Vidican
Cc: [EMAIL PROTECTED]
Subject: Re: [Samba] File locks db (manually removing locks)
>Is there any utility to manually manipulate the db file these locks are
>s
>Is there any utility to manually manipulate the db file these locks are
>stored in; or will simply deleting the db file after stopping all samba
>processes, allow the new instance to create a fresh (empty) database? - How
>do we remove the locks marked as present which really aren't?
Why would y
e: [Samba] File locks db (manually removing locks)
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 th
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 s
