[Samba] Killing an open file doesnt work? (i dont know how to..!)
jfenner at sino.de
Mon Jul 1 03:39:03 GMT 2002
> This sounds like you could corrupt data. Just guessing. Are you
fake oplocks= no
oplock break wait time=0
this is what we use at the moment but we had the problem already
before we used oplocks.
> On Mon, Jul 01, 2002 at 08:45:40AM +0200, Jan Fenner wrote:
> > Hi all,
> > since we updated to to 2.2.2 (or .3??) we have a big problem.
> > Sometimes we need to 'kill' a locked file.
> > That means, a user left his w2k terminal, locked it and forgott to
> > close file.xls or file.doc.
> > In the past we just did:
> > smbstatus | grep "file.xls"
> > kill -9 <PID>
> > and the file was unlocked, so anybody could access it again.
> > Since the update (version we use now is: 2.2.5 on RedHat 7.2) we
> > the same but infact all connections of the PID (user) are killed
> > any file this user has locked remains locked and stays locked, as
> > as he doesn't close it.
> > Is kill -9 the worst way? Is there an other way? We didnt found
> > other way but hardly need that 'feature'.
> > Thanks for any help
> > Regrades,
> > - Jan Fenner
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions: http://lists.samba.org/mailman/listinfo/samba
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
More information about the samba