mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Date: Mon, 27 Dec 2004 11:22:36 +1100	[thread overview]
Message-ID: <16847.21964.789391.93324@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20041226030957.GA8512@work.bitmover.com>

Larry McVoy writes:

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

Yes, I had bk pull and bk export fail for me yesterday.  If I did a bk
pull it would sit there for a while and then put up a window saying it
couldn't get to lease.openlogging.org.  If I clicked OK, after a while
another window would come up with a similar message (but I didn't read
it carefully).

> It is true that both servers are at our offices so if the network had been
> down you would have been out of luck.

I did a traceroute and it looked like a network problem.  From memory
it stopped after about 10 hops, and it seems to be 17 hops to
openlogging.org from here now.

My setup is possibly a little unusual, and may be causing problems for
your lease code: I have my BK repos on a firewire-attached disk, which
I move from machine to machine - specifically, it commutes between home
and work with me.

Paul.

  parent reply	other threads:[~2004-12-27  9:31 UTC|newest]

Thread overview: 30+ 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
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 [this message]
2004-12-26  2:21 ` 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=16847.21964.789391.93324@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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

all inboxes | Powered by JetHome®