Larry Jones wrote:
Derek Robert Price writes:Ah. Okay. Thanks.
What happens right now if two tag readers are trying to upgrade to write-locks at the same time? Can they both have a read lock in the same directory and thus each prevent the other from upgrading to a write-lock?Right now, that code has been replaced due to that exact problem (which
of course didn't occur to me *before* I checked in the change, only
afterwards). Now, start_recursion takes a locktype argument that tells
it whether to read or write lock each directory as it's processed.
Seems to me an "I'm waiting to upgrade to a write lock" lock would work just as well. Such a lock could prevent the creation of any other locks and other readers waiting for an upgrade could release their read locks in preference of the first server with an "upgrade" lock.
I haven't studied the problem though. Would that be any more efficient than what you did?
Derek
--
*8^)
Email: [EMAIL PROTECTED]
Get CVS support at <http://ximbiot.com>!
--
Cynic: Someone who smells the flowers and looks for the casket
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
