From: Larry McVoy <lm@bitmover.com>
To: M?ns Rullg?rd <mru@inprovide.com>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: lease.openlogging.org is unreachable
Date: Sun, 26 Dec 2004 10:18:37 -0800 [thread overview]
Message-ID: <20041226181837.GA28786@work.bitmover.com> (raw)
In-Reply-To: <yw1xmzw19bnn.fsf@inprovide.com>
On Sun, Dec 26, 2004 at 07:06:52PM +0100, M?ns Rullg?rd wrote:
> Larry McVoy <lm@bitmover.com> writes:
>
> > On Sun, Dec 26, 2004 at 11:26:42AM +0100, M?ns Rullg?rd wrote:
> >> I've been bitten by that one, as I occasionally work off-line. Is
> >> there some way I can make BK renew the leases a week or so before they
> >> expire?
> >
> > In theory, we do that already. By you can always do a "bk lease renew"
> > and that will get you a new lease. "bk lease show" will show you your
> > lease.
>
> Looking closer, the problem is that my hostname keeps changing,
> depending on which network the laptop is on, if any. I guess the
> simple solution is to remember to renew the lease for the no-net
> hostname before going offline.
The other answer, which I'm happy to consider, is to come up with a unique
id on a per host basis and use that for the leases. That's not a fun task,
does anyone have code (BSD license please) which does that?
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2004-12-26 18:18 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
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 [this message]
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=20041226181837.GA28786@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@inprovide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.