Re: Lock contention executing cvs log

[Larry Jones]

MacDonald, Ian writes:
>
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="===============91921517666352637=="

Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!

> Shouldn't cvs simply be using "read" locks while executing the log
> command? 

It should, and it is.

> If that's the case, why is there a contention for the "read" locks?

Because you need an exclusive lock to create a read lock.  The exclusive
lock is only held for a very short time (just long enough to create the
read lock), but it's still possible for there to be contention for it.

-Larry Jones

I must have been delirious from having so much fun. -- Calvin