From owner-freebsd-hackers Tue May 22 4: 0:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 8C5CE37B424 for ; Tue, 22 May 2001 04:00:10 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0077.cvx21-bradley.dialup.earthlink.net [209.179.192.77]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id HAA05502; Tue, 22 May 2001 07:00:06 -0400 (EDT) Message-ID: <3B0A46CF.9D0CB622@mindspring.com> Date: Tue, 22 May 2001 04:00:31 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: hackers@FreeBSD.ORG Subject: Re: -R for make update ? References: <20010521194828.A789@freebie.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Wilko Bulte wrote: > > Hi > > 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. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message