Date: Tue, 19 May 1998 02:30:54 -0700 (PDT) From: Dmitry Kohmanyuk <dk@dog.farm.org> To: nate@mt.sri.com (Nate Williams) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: nfs exported FreeBSD cvs repository, mounted on client, update problems Message-ID: <199805190930.CAA24138@dog.farm.org>
next in thread | raw e-mail | index | archive | help
In article <199805180342.VAA22777@mt.sri.com> you wrote:
> > How difficult would it be for CVSup to lock the entire repository while
> > it's running? Is it worth the effort?
> Easy, but expensive, since CVS doesn't use a global lock for all
> commits. It would have to lock every directory in the entire tree down,
> something CVS isn't willing to do.
how about locking directory while updating its files? From cvsup logs, it
looks like it always does a breadth-first traversal... so, it would
require locking and unlocking {of each directory in which files were updated}
only once.
--
Others run "biff" to alert them about new mail. I run /bin/true
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805190930.CAA24138>