Exclusive Locking ... per lock type?

Did section 8.10.6 of 2518 meant to say that an exclusive
lock will fail if there already is a lock *of that locktype* on that
resource, or if there is *any* exclusive lock there?

I can see arguments for both directions, and implementors  probably haven't
thought that much about it since everybody is just doing write locks,
but I assume the authors had one or the other in mind?

Cheers,
Geoff

Received on Monday, 27 December 1999 16:39:18 UTC