Date: Tue, 22 May 2001 12:59:19 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Wilko Bulte <wkb@freebie.demon.nl>, hackers@FreeBSD.ORG Subject: Re: -R for make update ? Message-ID: <20010522125919.D27648@xor.obsecurity.org> In-Reply-To: <3B0A46CF.9D0CB622@mindspring.com>; from tlambert2@mindspring.com on Tue, May 22, 2001 at 04:00:31AM -0700 References: <20010521194828.A789@freebie.demon.nl> <3B0A46CF.9D0CB622@mindspring.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, May 22, 2001 at 04:00:31AM -0700, Terry Lambert wrote: > > 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. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7CsUWWry0BWjoQKURAhGLAKDKnJVAHd6OSglnR08WSvCw2FApZwCgzKKq PkSIP54dYtdroDQbYTxEn+U= =Zz2Z -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010522125919.D27648>