lock_unlock() problem?

[Lawrence Greenfield]

--On Thursday, November 21, 2002 3:37 PM -0500 DAVID G MCMURTRIE 
<dgm+ at pitt.edu> wrote:

> On Thu, 21 Nov 2002, Rob Siemborski wrote:
>
>> "Upgrade your version of cyrus"
>>
>> Many many many locking and performance improvements have been made since
>> then, and spending the time to diagnose the problems with that code base
>> just isn't time well spent.
>
> Agreed.  However, this exact piece of code still exists in the latest
> version.  I'm curious whether there's a reason to not check the return
> code of fcntl on the unlock, but it's checked when you lock.

Yeah, it's highly unlikely that this is the cause of your problem. Usually 
this is due to a client hanging in an unexpected place and the server 
hasn't even tried to remove it's lock.

I'm surprised that Unix is allowed to return EINTR here on a local 
filesystem and it is something we should check.

Larry