From owner-freebsd-current Tue Mar 28 19:26:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DF4F737B641 for ; Tue, 28 Mar 2000 19:26:39 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA12083; Tue, 28 Mar 2000 19:26:39 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA04802; Tue, 28 Mar 2000 19:26:38 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 28 Mar 2000 19:26:38 -0800 (PST) Message-Id: <200003290326.TAA04802@vashon.polstra.com> To: Doug@gorean.org Subject: Re: cvs repository nits and gnats In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Doug Barton wrote: > > > 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. > > My gut feeling is that it's a timing issue. I happened to have > been cvsup'ing when someone actually had a lock on something in the > repository. Still I think it's odd that A) the cvsup "mirrors" of the > master repository picked up these files, B) that my cvsup of the > repository picked them up, and C) having picked them up, it didn't delete > them when they were deleted from the real respository. FWIW, I always use > cvsup7, and I found these lock files in both my home and work copies. I think you may be misinterpreting the symptoms, because I don't know of any way for lock files to propagate off of freefall with CVSup. All lock files are specifically excluded in the server's config files -- they won't even make it to cvsup-master, let alone to the mirrors such as cvsupN.freebsd.org. What were the names of the files you thought were lock files? It sounds to me like maybe they were created by something on your local system -- not mirrored via CVSup. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message