From owner-freebsd-current@FreeBSD.ORG Tue Jan 13 22:53:05 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 3C11216A4CE for ; Tue, 13 Jan 2004 22:53:05 -0800 (PST) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D9F643D2F for ; Tue, 13 Jan 2004 22:53:03 -0800 (PST) (envelope-from stijn@pcwin002.win.tue.nl) Received: from pcwin002.win.tue.nl (orb_rules@localhost [127.0.0.1]) by pcwin002.win.tue.nl (8.12.10/8.12.10) with ESMTP id i0E6tf4x042335; Wed, 14 Jan 2004 07:55:41 +0100 (CET) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.12.10/8.12.10/Submit) id i0E6tfXm042334; Wed, 14 Jan 2004 07:55:41 +0100 (CET) (envelope-from stijn) Date: Wed, 14 Jan 2004 07:55:41 +0100 From: Stijn Hoop To: Garance A Drosihn Message-ID: <20040114065541.GE39353@pcwin002.win.tue.nl> References: <20040112132544.D54803@pooker.samsco.home> <20040113225632.GA80120@memnoch.jk.homeunix.net> <200401140029.27160.max@love2party.net> <20040114004632.GB80120@memnoch.jk.homeunix.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NU0Ex4SbNnrxsi6C" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Bright-Idea: Let's abolish HTML mail! cc: freebsd-current@freebsd.org cc: John Kennedy Subject: 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 06:53:05 -0000 --NU0Ex4SbNnrxsi6C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 explanati= on for this or is it just an unfixed bug in CVS? --Stijn --=20 Tact, n.: The unsaid part of what you're thinking. --NU0Ex4SbNnrxsi6C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFABOftY3r/tLQmfWcRAtYiAKCz6VI2K48uIflMIr7u37K+/gNebACeIESz B3l/tgrGnADTJLjUwApJtoE= =S3yA -----END PGP SIGNATURE----- --NU0Ex4SbNnrxsi6C--