public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Jim Meyering <jim@meyering.net>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>, overseers@sourceware.org
Subject: Re: git://sourceware.org/git/glibc.git is having trouble?
Date: Sun, 04 Mar 2012 19:36:00 -0000	[thread overview]
Message-ID: <20120304193611.GC23937@elastic.org> (raw)
In-Reply-To: <87eht89o24.fsf@rho.meyering.net>

Hi -

On Sun, Mar 04, 2012 at 08:13:55PM +0100, Jim Meyering wrote:
> [...]
> > I also had similar trouble last Friday.
> 
> I heard that due to recent DoS problems, someone imposed a new
> limit on maximum number of connections.  [...]

Yes, I set a loadavg <= limit for anon-git.

> However, I've just tried to update my own glibc clone
>   Sun Mar  4 20:12:13 CET 2012
> and it succeeded.

Load fluctuates dramatically on the machine.  I'm hoping that with the
new RHEL6 boxes, with cgroups, we won't have to trade services off
against each other quite so much.

- FChE

      reply	other threads:[~2012-03-04 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 18:48 Paul Pluzhnikov
2012-03-04 19:14 ` Jim Meyering
2012-03-04 19:36   ` Frank Ch. Eigler [this message]

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=20120304193611.GC23937@elastic.org \
    --to=fche@elastic.org \
    --cc=jim@meyering.net \
    --cc=overseers@sourceware.org \
    --cc=ppluzhnikov@google.com \
    /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).