Question about locking

[Makis Marmaridis]

Joe,

In my previous job (at a large Uni here in Australia) we used to use Eudora
as well and even though the mailboxes were on NT Servers there, the problem
with the OWNER.LOK file left behind existed for us then too.

I had seen this same problem several times using Windows 95, 98, NT 4.0 and
even Win2K clients.

We used to work around it by making the user logon script check for the
existance of the file and remove it if its was there.

HTH,

Cheers,
Makis.

-----Original Message-----
From: samba-technical-admin at lists.samba.org
[mailto:samba-technical-admin at lists.samba.org]On Behalf Of Joe Meslovich
Sent: Friday, 27 July 2001 6:16 AM
To: jeremy at valinux.com; samba-technical at lists.samba.org
Subject: Question about locking


Jeremy,
	My campus uses the Eudora email client our client PCs are Win 2k
and the servers are Solaris 8 servers running Samba 2.2.1a. The eudora
program creates a file called OWNER.LOK to ensure that only one user is
accessing a set of mailboxes at a time. That file exists while the
mailboxes are in use and it is supposed to disappear after the program
closes. What we have seen are OWNER.LOK files sticking around even after
the program is closed. When I did an smbstatus on a perticular user that
was having problems with that file sticking around I got this output:

8476   DENY_NONE  RDWR       LEVEL_II  /export/home/facstaff/jatkins/eudo
ra/OWNER.LOK   Thu Jul 26 11:57:18 2001
8476   DENY_NONE  RDWR       LEVEL_II  /export/home/facstaff/jatkins/eudo
ra/OWNER.LOK   Thu Jul 26 11:55:54 2001

	The occurance of the dual LEVEL_II oplocks is what concerns me.
How can a single process lock a file in a LEVEL_II lock twice?


							Joe Meslovich

----------------------------------------------------------------------------
Joe Meslovich						joe at bridgewater.edu
Associate Network/Systems Engineer	                College Box 499
Tel: (540) 828 - 5343