public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: overseers@sourceware.org
Cc: Dave Wysochanski <dwysocha@redhat.com>,
	 "Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: Upstream cvs repository corruption?
Date: Mon, 24 Sep 2007 14:28:00 -0000	[thread overview]
Message-ID: <87wsuguoib.fsf@rho.meyering.net> (raw)
In-Reply-To: <20070924131507.GA29811@ednor.casa.cgf.cx> (Christopher Faylor's message of "Mon, 24 Sep 2007 09:15:08 -0400")

Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> 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?

  reply	other threads:[~2007-09-24 14:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1190637220.4431.2.camel@linux-cxyg>
2007-09-24 13:04 ` Jim Meyering
2007-09-24 13:15   ` Christopher Faylor
2007-09-24 14:28     ` Jim Meyering [this message]
2007-09-24 14:39       ` Christopher Faylor
2007-09-24 15:06         ` Jim Meyering
2007-09-24 15:34           ` Christopher Faylor
2007-09-24 16:50             ` Jim Meyering

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wsuguoib.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=agk@redhat.com \
    --cc=dwysocha@redhat.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).