samba - Jun 2002 - Killing an open file doesnt work? (i dont know how to..!)

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 do
the same but infact all connections of the PID (user) are killed but
any file this user has locked remains locked and stays locked, as long
as he doesn't close it.

Is kill -9 the worst way? Is there an other way? We didnt found any
other way but hardly need that 'feature'.


Thanks for any help


Regrades,
- Jan Fenner

This sounds like you could corrupt data.  Just guessing. Are you using oplocks?

Joel

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 do
> the same but infact all connections of the PID (user) are killed but
> any file this user has locked remains locked and stays locked, as long
> as he doesn't close it.
> 
> Is kill -9 the worst way? Is there an other way? We didnt found any
> 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

>
> Very dangerous.  As an admin, you can unlock his 2k workstation and
close
> his file.  If he is geographically remote, get vnc installed.
In no case i will run through the complete building and log out any
user if i have to check files. Those who dont save will do it again
the next day :-)
Anyway .. there must be a way to unlock a file so other can write it,
isnt it ?

-jan