|
From: | Derek Robert Price |
Subject: | Re: CVS update: MODIFIED: src ... |
Date: | Fri, 08 Nov 2002 15:01:50 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 |
Larry,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?
Derek -- *8^) Email: derek@ximbiot.com Get CVS support at <http://ximbiot.com>! -- Black holes are where God divided by zero. scjones@cvshome.org wrote:
User: scjones Date: 02/10/03 20:35:31Modified: src ChangeLog lock.c tag.c Log: * lock.c (readers_exist): Ignore our own read lock, if any, to allow upgrading an existing read lock to a write lock. * tag.c (rtag_proc, rtag_fileproc, tag_fileproc): Rather than locking the entire tree, have start_recursion establish read locks and then upgrade the read lock to a write lock (so only one directory is locked at a time).
[Prev in Thread] | Current Thread | [Next in Thread] |