Re: New email address

[Riley Williams]

Hi Brian.

>>> Brian Behlendorf tells me that Collab Net will be supporting the
>>> bandwidth and hardware for cvshome.org for an indefinite period.

>> Are you sure of this? As of yesterday morning, I've been unable to
>> get to cvshome.org either by web or cvs pserver, so as far as I can
>> tell, it's already dead...

> The server is definitely up - we moved it to a new network location
> on Friday and had some resulting routing issues, causing some hefty
> downtime then, but it should be back up. If you get a clearer idea
> of in what way the system is "down" for you (DNS won't resolve or
> goes to an older IP address, IP address can't be reached, IP address
> is reachable but connectivity is poor, or IP address connectivity is
> good but nothing's listening on port 80) then let me know and I'll
> look at it.

When I had a look for it on Sunday morning, I found the following
mappings (from memory):

        cvs.cvshome.org         127.0.0.9
        www.cvshome.org         127.0.0.15

Both were 127.0.0.* addresses, and neither was valid - the only valid
127.* addresses here are 127.0.0.1 and 127.0.0.255 !!!

I've just tried again, and see the following mapping at the moment:

        cvs.cvshome.org         64.125.132.231  64.125.132.213
        www.cvshome.org         64.125.132.231

I'm not sure whether there should be two IP's for the cvs server, but I
see two in response to the `host cvs.cvshome.org` command here, although
only one shows up to `host www.cvshome.org` at this time.

Based on that, I've just done `cvs update -d -P` from the directory I
downloaded the CVS tree to, and get...

===8<=== CUT ===>8===

$ cvs update -d -P
cvs [update aborted]: connect to cvs.cvshome.org(64.125.132.231):2401
        failed: connection refused
$

===8<=== CUT ===>8===

...which is the same message, but with an IP address that is at least
valid - the previous one was not. In case it helps, I've enclosed a
traceroute to cvs.cvshome.org when it selected that IP...

> CollabNet will continue to support the CVS community and codebase by
> hosting cvshome.org for the indefinite future. The bandwidth load
> is pretty modest, we're OK on hardware allocations, so it's not a
> problem. Derek's indicated a willingness to continue administering
> it, which I definitely appreciate.

That I'm certainly glad to hear.

> These economic times are very tough, and last week CollabNet had to
> let some very valuable people go, including Derek. He assisted us
> tremendously with some pretty deep CVS problems, much of the results
> of which ended up as contributions back (on CVS and other projects
> as well). If any of you are using CVS in demanding situations and
> looking to hire a guru, I would recommend him highly.

If I was in a position to do so, I'm sure I would. Ufortunately, I'm
also the possessor of far too much free time, for similar reasons :(

Best wishes from Riley.

cvs.log
Description: Traceroute to cvs.cvshome.org