public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: BKCVS broken ?
Date: Fri, 18 Mar 2005 03:07:50 +0000 (UTC)	[thread overview]
Message-ID: <d1dgm6$ma5$1@terminus.zytor.com> (raw)
In-Reply-To: 20050317154434.GA24378@bitmover.com

Followup to:  <20050317154434.GA24378@bitmover.com>
By author:    lm@bitmover.com (Larry McVoy)
In newsgroup: linux.dev.kernel
>
> I'll check into it.  We've been having problems with connecting to 
> master.kernel.org, yup, here you go, anyone else seeing this?
> 
> From lm@slovax.bitmover.com  Thu Mar 17 05:06:57 2005
> Date: Thu, 17 Mar 2005 05:00:57 -0800
> From: root@slovax.bitmover.com (Cron Daemon)
> To: lm@slovax.bitmover.com
> Subject: Cron <lm@slovax> /bk-cvsexport/src/UPDATE
> 
> Read from remote host master.kernel.org: Connection timed out
> 

Please Cc: any reports of badness on kernel.org to
ftpadmin@kernel.org; I would have seen this quicker that way.

Around the time the above happened the machine was pretty bogged down,
because we're preparing new hardware to replace the main server, and
were doing some very large copies.  It might have caused a timeout.

I notice a long login from you at approximately 14:00 PST; does that
mean this is no longer an issue?

	-hpa

  reply	other threads:[~2005-03-18  3:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 14:45 BKCVS broken ? Stelian Pop
2005-03-17 15:43 ` Catalin Marinas
2005-03-17 15:44 ` Larry McVoy
2005-03-18  3:07   ` H. Peter Anvin [this message]
2005-03-18  0:10 ` Larry McVoy
2005-03-18  5:50   ` Erik Andersen
2005-03-18  6:38     ` Larry McVoy
2005-03-18  9:00       ` Stelian Pop
2005-03-18 14:13         ` Larry McVoy
2005-03-18 14:21           ` Stelian Pop
2005-03-18 15:08             ` Hong Kong Phoey
2005-03-18 22:09               ` Stelian Pop
2005-03-19 14:52 ` Larry McVoy

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='d1dgm6$ma5$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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