From: Sam Ravnborg <sam@ravnborg.org>
To: Larry McVoy <lm@work.bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: [BK] status
Date: Tue, 13 Apr 2004 17:36:32 +0200 [thread overview]
Message-ID: <20040413153631.GA2385@mars.ravnborg.org> (raw)
In-Reply-To: <20040413150435.GA12004@work.bitmover.com>
>
> Other than the up/down problems, have any of you noticed bkbits being
> slower since the move (which happened Friday or Saturday, it's sort of
> a blur)?
I see no slowdown.
But this morning (something like 8 hours ago) I could not pull from
linux.bkbits.net - it just silently exited.
When trying to access www.bkbits.net I got a full list of projects,
but when I tried to access one of the projects (when it starts using port
8080) I after a while got a message that "I had not purchased BKWeb" or
something similar. I took this as overload but now you ask I report it.
Sam
next prev parent reply other threads:[~2004-04-13 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 15:04 [BK] status Larry McVoy
2004-04-13 15:36 ` Sam Ravnborg [this message]
2004-04-13 17:28 ` Larry McVoy
2004-04-13 17:29 ` Andy Isaacson
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=20040413153631.GA2385@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.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