From owner-freebsd-hackers Wed May 23 14: 8:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 2CF2437B423 for ; Wed, 23 May 2001 14:08:44 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 152fs1-0004v3-00; Wed, 23 May 2001 21:08:42 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f4N6XL304311; Wed, 23 May 2001 08:33:21 +0200 (CEST) (envelope-from wkb) Date: Wed, 23 May 2001 08:33:21 +0200 From: Wilko Bulte To: Kris Kennaway Cc: Nate Williams , Terry Lambert , hackers@FreeBSD.ORG Subject: Re: -R for make update ? Message-ID: <20010523083321.A4293@freebie.demon.nl> References: <20010521194828.A789@freebie.demon.nl> <3B0A46CF.9D0CB622@mindspring.com> <20010522125919.D27648@xor.obsecurity.org> <15114.51414.50651.695529@nomad.yogotech.com> <20010522144242.A29988@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010522144242.A29988@xor.obsecurity.org>; from kris@obsecurity.org on Tue, May 22, 2001 at 02:42:42PM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, May 22, 2001 at 02:42:42PM -0700, Kris Kennaway wrote: > On Tue, May 22, 2001 at 02:15:18PM -0600, Nate Williams 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. > > > > 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...) > > Yes, using rsh/ssh is also slow, but we were talking about *local* > access, which has none of those drawbacks. -R makes cvs operations go Yes, this is a local repo indeed. > quite a bit faster, and AFAIK is perfectly safe if you're using a > private repo for which you know there will be no contention. W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte Powered by FreeBSD/alpha http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message