I have some users who routinely open files, lock their workstations, and leave the office. In some situations another user needs write-access to the file.
I know that I can use smbstatus to find and kill the PID associated with the annoying user's samba session and release the oplock on that particular file. This has the semi-unfortunate side-effect of killing the user's entire session. Is there a way to do this for only a single file?
I know that I can use smbstatus to find and kill the PID associated with the annoying user's samba session and release the oplock on that particular file. This has the semi-unfortunate side-effect of killing the user's entire session. Is there a way to do this for only a single file?