From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Jim Meyering <jim@meyering.net>,
overseers@sourceware.org, Dave Wysochanski <dwysocha@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: Upstream cvs repository corruption?
Date: Mon, 24 Sep 2007 14:39:00 -0000 [thread overview]
Message-ID: <20070924143952.GA29974@ednor.casa.cgf.cx> (raw)
In-Reply-To: <87wsuguoib.fsf@rho.meyering.net>
On Mon, Sep 24, 2007 at 04:27:56PM +0200, Jim Meyering wrote:
>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
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.
>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
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.
cgf
next prev parent reply other threads:[~2007-09-24 14:39 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
2007-09-24 14:39 ` Christopher Faylor [this message]
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=20070924143952.GA29974@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=agk@redhat.com \
--cc=dwysocha@redhat.com \
--cc=jim@meyering.net \
--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).