From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7509 invoked by alias); 24 Sep 2007 15:06:42 -0000 Received: (qmail 7500 invoked by uid 22791); 24 Sep 2007 15:06:41 -0000 X-Spam-Check-By: sourceware.org Received: from mx.meyering.net (HELO mx.meyering.net) (82.230.74.64) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 24 Sep 2007 15:06:39 +0000 Received: by rho.meyering.net (Acme Bit-Twister, from userid 1000) id 7911753FC0; Mon, 24 Sep 2007 17:06:37 +0200 (CEST) From: Jim Meyering To: overseers@sourceware.org Subject: Re: Upstream cvs repository corruption? In-Reply-To: <20070924143952.GA29974@ednor.casa.cgf.cx> (Christopher Faylor's message of "Mon, 24 Sep 2007 10:39:52 -0400") References: <1190637220.4431.2.camel@linux-cxyg> <87r6kow6yn.fsf@rho.meyering.net> <20070924131507.GA29811@ednor.casa.cgf.cx> <87wsuguoib.fsf@rho.meyering.net> <20070924143952.GA29974@ednor.casa.cgf.cx> Date: Mon, 24 Sep 2007 15:06:00 -0000 Message-ID: <87r6koumpu.fsf@rho.meyering.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00108.txt.bz2 Christopher Faylor wrote: > On Mon, Sep 24, 2007 at 04:27:56PM +0200, Jim Meyering wrote: >>Christopher Faylor wrote: >>> On Mon, Sep 24, 2007 at 03:04:00PM +0200, Jim Meyering wrote: >>>>I nearly Cc'd Frank about this (to thank him for helping to set up git >>>>recently :-), but thought better of it, and am Cc'ing overseers, instead. >>>> >>>>Of course, the real solution is to switch to git, >>>>but lvm will have to wait a few weeks for that ;-) >>> >>> In the meantime I've noticed quite a few long-running processes owned by >>> you running on sourceware. Having long-running user-owned processes is >> >>As far as I know, there was one incident. Frank told me you noticed some, >>and I killed them right away. Did I not kill them quickly enough? :-) 1/2 > > No, actually, I asked about them and, AFAIK, never got a response. The > issue wasn't with the processes running. Random users should not be > starting long running daemon processes on sourceware. For what it's worth, I'm _not_ running any daemon processes from my account on sourceware. The long-running processes you spotted were the result of a bug somewhere, and not related to the git "service". The programs involved were converting cvs deltas to git ones and importing them into a git repository. Not actually _using_ the git server at all, but rather, adding to a repo that is used by the git server. >>About 10 minutes elapsed on Saturday, between when I heard about the >>problem and when they were all dead. >> >>BTW, I don't know what made that happen (a defunct cvs process was >>at the root of each of two process trees). If it happens again, I'll >>investigate. Normal mirror-sync runs are very quick. >> >>> not really a good practice given the principle of "what happens if he's >>> hit by a bus?" >> >>They weren't consuming significant resources, so >>I don't see the problem with those few delinquent processes. > > I didn't say anything about resources. User "meyring" should not be > running daemons or other long-running processes. If we are going to be > running git then it should be run from a user-neutral account. I was Um... git is properly installed, and does not in any way rely on my personal account. > trying to find out what that should actually be. There is no need to > rationalize the need. I just want to figure out how this should > actually be set up. And, I thought that if we chose another account > with different access rights it might actually solve the problem. Chris, >From the tone of your messages, I fear I may have done something to offend you. If so, please rest assured that whatever I did was not intended to rustle any feathers.