From: James Bottomley <James.Bottomley@SteelEye.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lease.openlogging.org is unreachable
Date: Sun, 26 Dec 2004 10:12:10 -0600 [thread overview]
Message-ID: <1104077531.5268.32.camel@mulgrave> (raw)
> 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?
I believe I've reported this problem to you and support@bitmover.com
several times.
There's something in BK that refuses to work when it can't contact
lease.openlogging.org, regardless of whether you just renewed the lease
or not. This keeps biting me when I try to use BK disconnected from the
internet (usually while travelling).
This problem is certainly my single biggest headache with BK since it
means I can't go through my backlog of email and build the SCSI BK tree
when I'm travelling (which is often the only time I have available for
doing it).
My current version is bk 3.2.3 but it's been a problem on all prior
versions I've used as well.
James
next reply other threads:[~2004-12-26 16:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 16:12 James Bottomley [this message]
2004-12-26 16:27 ` lease.openlogging.org is unreachable Larry McVoy
2004-12-26 16:43 ` James Bottomley
2004-12-26 17:19 ` [BK] disconnected operation Larry McVoy
2004-12-26 18:25 ` James Bottomley
2004-12-26 18:35 ` Larry McVoy
2004-12-26 18:46 ` James Bottomley
2004-12-26 18:41 ` Zwane Mwaikambo
2004-12-26 20:30 ` Martin Dalecki
2004-12-26 20:20 ` Martin Dalecki
2004-12-28 14:33 ` Ricky Beam
2004-12-29 5:16 ` Kyle Moffett
2004-12-29 6:00 ` Ricky Beam
2004-12-28 9:17 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 0:36 lease.openlogging.org is unreachable David Brownell
2004-12-26 13:38 Chuck Ebbert
2004-12-25 6:20 Chuck Ebbert
2004-12-25 12:24 ` Alan Cox
2004-12-26 1:15 ` Larry McVoy
2004-12-26 1:12 ` 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-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=1104077531.5268.32.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--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