Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Mar 2000 10:55:01 -0800 (PST)
From:      Kris Kennaway <kris@FreeBSD.org>
To:        Doug Barton <Doug@gorean.org>
Cc:        freebsd-current@freebsd.org, Peter Wemm <peter@netplex.com.au>
Subject:   Re: cvs repository nits and gnats
Message-ID:  <Pine.BSF.4.21.0003281052550.46676-100000@freefall.freebsd.org>
In-Reply-To: <38E08D12.DC350F14@gorean.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <forsythe@alum.mit.edu>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003281052550.46676-100000>