public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Chuck Ebbert <76306.1226@compuserve.com>,
	Larry McVoy <lm@bitmover.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: lease.openlogging.org is unreachable
Date: Sat, 25 Dec 2004 19:09:57 -0800	[thread overview]
Message-ID: <20041226030957.GA8512@work.bitmover.com> (raw)
In-Reply-To: <20041226011222.GA1896@work.bitmover.com>

The interesting thing is that the code already has a backup in it and I just
checked that code path and it works.

Has anyone else been shut down because of lease.openlogging.org being down
and if so what version of BK were you running please?

It is true that both servers are at our offices so if the network had been
down you would have been out of luck.  We'll create some more backups and
scatter them around the US, that's no problem.  But if the logic in the 
code to get them is busted then we need to fix that.

Things should be stabilized now, the machine went up and down a few times
after my last "it's OK mail", it turned out we had a dieing ethernet card;
it's been replaced and we seem stable now.  
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

  reply	other threads:[~2004-12-26  3:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-25  6:20 lease.openlogging.org is unreachable Chuck Ebbert
2004-12-25 12:24 ` Alan Cox
2004-12-26  1:15   ` Larry McVoy
2004-12-26 12:22     ` bkcvs seems to have stale data [was Re: lease.openlogging.org is unreachable] Pavel Machek
2004-12-26 16:00       ` Larry McVoy
2004-12-26  1:12 ` lease.openlogging.org is unreachable Larry McVoy
2004-12-26  3:09   ` Larry McVoy [this message]
2004-12-26 10:26     ` Måns Rullgård
2004-12-26 16:02       ` Larry McVoy
2004-12-26 18:06         ` Måns Rullgård
2004-12-26 18:18           ` Larry McVoy
2004-12-26 20:26             ` Martin Dalecki
2004-12-26 20:37             ` Alan Cox
2004-12-26 22:12               ` Martin Dalecki
2004-12-26 23:01                 ` Florian Weimer
2004-12-26 23:13                   ` Martin Dalecki
2004-12-27  0:03                     ` Chris Wedgwood
2004-12-27  0:11                       ` Martin Dalecki
2004-12-27  0:31             ` Horst von Brand
2004-12-27  0:53               ` Chris Wedgwood
2004-12-27  1:38               ` Martin Dalecki
2004-12-27  1:41               ` Larry McVoy
2004-12-27  2:40                 ` Martin Dalecki
2004-12-27  2:43                   ` Larry McVoy
2004-12-27  2:59                     ` Martin Dalecki
2004-12-28 14:59                       ` Ricky Beam
2004-12-27  8:48                     ` Bernd Eckenfels
2004-12-28 14:55                   ` Ricky Beam
2004-12-27  0:22     ` Paul Mackerras
2004-12-26  2:21 ` lease.openlogging.org is unreachable Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2004-12-26 13:38 Chuck Ebbert
2004-12-26 16:12 James Bottomley
2004-12-26 16:27 ` Larry McVoy
2004-12-26 16:43   ` James Bottomley
2004-12-30  0:36 David Brownell

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=20041226030957.GA8512@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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