From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16069 invoked by alias); 24 Sep 2007 14:28:02 -0000 Received: (qmail 16062 invoked by uid 22791); 24 Sep 2007 14:28:02 -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 14:27:58 +0000 Received: by rho.meyering.net (Acme Bit-Twister, from userid 1000) id 533F854CA4; Mon, 24 Sep 2007 16:27:56 +0200 (CEST) From: Jim Meyering To: overseers@sourceware.org Cc: Dave Wysochanski , "Alasdair G. Kergon" Subject: Re: Upstream cvs repository corruption? In-Reply-To: <20070924131507.GA29811@ednor.casa.cgf.cx> (Christopher Faylor's message of "Mon, 24 Sep 2007 09:15:08 -0400") References: <1190637220.4431.2.camel@linux-cxyg> <87r6kow6yn.fsf@rho.meyering.net> <20070924131507.GA29811@ednor.casa.cgf.cx> Date: Mon, 24 Sep 2007 14:28:00 -0000 Message-ID: <87wsuguoib.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/msg00106.txt.bz2 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 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. If you mean the mirroring service, I see that as a short-term project, since Alasdair is interested in converting to git. If the mirroring were expected to last more than a few weeks, I'd be interested in moving the cron jobs to a role-based account. If you'd prefer, I'll do that anyway, but it doesn't seem worthwhile at this point. > Should your git-related processes be owned by someone other than you? > Would that solve both problems?