From owner-freebsd-current Tue Mar 28 10:55: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9819937B7A1; Tue, 28 Mar 2000 10:55:02 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id KAA47144; Tue, 28 Mar 2000 10:55:02 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 28 Mar 2000 10:55:01 -0800 (PST) From: Kris Kennaway To: Doug Barton Cc: freebsd-current@freebsd.org, Peter Wemm Subject: Re: cvs repository nits and gnats In-Reply-To: <38E08D12.DC350F14@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Mar 2000, Doug Barton wrote: > src/TODO-2.1, src/usr.sbin/xntpd, etc. There were a large number in > contrib, probably detritus from imports, etc. I'm not sure if this is > significant, it obviously doesn't do any harm. I just thought I'd > mention it. CVS has no concept of removing a directory (possibly excepting repository surgery), so unless you pass the -P option (prune empty directories) you get stuck with all of the old ones. > Slightly more serious was the presence of various lock > files/directories. Specifically, one in src/games/primes killed my co as > an unpriviliged user because it was set 700 and owned by root. The co > failed because it couldn't create a lock file. I did a 'find . -name > \*\#\* in my CVSROOT and found several other files like this. Deleting > them did no harm, and they didn't return when I ran cvsup again. I havent seen this. > Finally, a question. I'm doing my cvs co/update on this machine > remotely via rsh (within our secure network of course). When I start the > update it creates an entire src directory tree in /tmp. This takes a > great deal of time, so I'm wondering if this can be avoided somehow? I'm > doing the cvs rsh as root on the client machine, and as an unpriviliged > user on the cvs server machine. I ran into this the other day and was advised to mount the CVS repository via NFS instead of accessing it via rsh. This indeed solves the problem. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message