From owner-freebsd-current@FreeBSD.ORG Wed Jan 14 07:23:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C86DD16A4CF for ; Wed, 14 Jan 2004 07:23:07 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5233743D68 for ; Wed, 14 Jan 2004 07:23:03 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i0EFLMUd046688; Wed, 14 Jan 2004 10:21:22 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i0EFLLIq046685; Wed, 14 Jan 2004 10:21:21 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 14 Jan 2004 10:21:21 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Stijn Hoop In-Reply-To: <20040114065541.GE39353@pcwin002.win.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Garance A Drosihn cc: John Kennedy Subject: Re: CVS filling /tmp (was Re: FreeBSD CVS Question (answered!)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2004 15:23:07 -0000 On Wed, 14 Jan 2004, Stijn Hoop wrote: > On Tue, Jan 13, 2004 at 08:30:32PM -0500, Garance A Drosihn wrote: > > The problem is how CVS itself works > > with a remote repository. If you're on machine A, and the > > repository is on machine B, then CVS will build a lot of > > information in /tmp on machine B when machine 'A' does a > > cvs-checkout of the entire tree. The issue is the same if > > you do that over 'rsh' instead of 'ssh'. I do not mind the > > overhead from encrypting the connection. > > I have seen this too, and sometimes this has prevented me from checking > out RELENG_4 or some such from a machine with a swap backed /tmp. Is > there *any* workaround other than using cvsup? Is there a logical > explanation for this or is it just an unfixed bug in CVS? While I'm not quite sure of the rhyme or reason, what's occuring is that CVS is creating a mirror directory layout of the subtree you're operating on in /tmp. This means you'll actually likely run out of inodes before space, FWIW. I usually set TMPDIR to point it at /usr/tmp to avoid this being a problem. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research