From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Subject: [BK] status
Date: Tue, 13 Apr 2004 08:04:35 -0700 [thread overview]
Message-ID: <20040413150435.GA12004@work.bitmover.com> (raw)
The various BK machines we host are in at their new location and seem
to have stabilized (famous last words, every time I say something like
that something crashes). kernel.bkbits.net, which is a shell account
machine for kernel developers, bk users or not, is not up yet, we've
had problems with that machine due to cooling and because we have a
much larger machine room we will be moving the guts of that machine to
a higher volume box to get better cooling. ETA on that should be today.
We're moving towards remote control of the critical machines. The machines
are already UPSed but they don't have serial consoles and/or remote power.
I've ordered a Sentry R2000 (model 203-0-1) which is supposed to be a pretty
nice remote power device. We'll get serial consoles on the machines so
that if they crash we can get the oops message and get some debugging help
(a couple of people, Bill Irwin in particular, went out of their way to
offer to help out with the the debugging. I mention it only because it
was nice to that kind of friendly offer and I'm grateful).
We are currently on one T1 line, we moved one of the two to the new office
and one is at the old office so we had some overlap in case something
went horribly wrong. It's clear that one T1 line isn't enough, you've
been keeping that T1 pretty full. We'll be back up to two in a few
weeks.
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)?
Oregon State's open source lab has repeated their offer to take over hosting
bkbits.net and we may take them up on that if we can ever work out the
logistics and you need the bandwidth.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next reply other threads:[~2004-04-13 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 15:04 Larry McVoy [this message]
2004-04-13 15:36 ` [BK] status Sam Ravnborg
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=20040413150435.GA12004@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.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