Date: Wed, 14 Jan 2004 07:55:41 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: Garance A Drosihn <drosih@rpi.edu> Cc: John Kennedy <jk@jk.homeunix.net> Subject: CVS filling /tmp (was Re: FreeBSD CVS Question (answered!)) Message-ID: <20040114065541.GE39353@pcwin002.win.tue.nl> In-Reply-To: <p0602046fbc2a4a50e4dd@[128.113.24.47]> References: <20040112132544.D54803@pooker.samsco.home> <20040113225632.GA80120@memnoch.jk.homeunix.net> <200401140029.27160.max@love2party.net> <20040114004632.GB80120@memnoch.jk.homeunix.net> <p0602046fbc2a4a50e4dd@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040114065541.GE39353>