Date: Tue, 22 May 2001 14:15:18 -0600 (MDT) From: Nate Williams <nate@yogotech.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Terry Lambert <tlambert2@mindspring.com>, Wilko Bulte <wkb@freebie.demon.nl>, hackers@FreeBSD.ORG Subject: Re: -R for make update ? Message-ID: <15114.51414.50651.695529@nomad.yogotech.com> In-Reply-To: <20010522125919.D27648@xor.obsecurity.org> References: <20010521194828.A789@freebie.demon.nl> <3B0A46CF.9D0CB622@mindspring.com> <20010522125919.D27648@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Is there any specific reason why one needs to be able to > > > write a lock to the CVS repo when running 'make update' > > > to get a freshly checked out source? > > > > Yeah: you aren't running your CVS server in "pserver" > > mode, and so are trying to do a lock, either in your > > local copy, or over NFS. > > > > If you run your repository in pserver mode, the CVS server > > will be connected to over the network, instead of attacking > > your CVS repo directly, and you won't have the problem you > > are seeing, since the cvs server will be able to get the > > lock, no problem. > > It will also be freakishly slow, and use massive amounts of temp > space. No slower than cvs using rsh/ssh, although it does tend to create alot of inodes in /tmp. (It doesn't create alot of temp space, other than what is used to create the directories...) Nate 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?15114.51414.50651.695529>