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.
traceroute to cvs.cvshome.org (64.125.132.231), 30 hops max, 38 byte packets
1 leopard.lns.birmingham.access.planet.net.uk (195.92.168.22) 113.715 ms *
1498.844 ms
2 * PBR-1.BRM.AS5388.NET (195.92.168.2) 111.201 ms *
3 BNR-2.BRM.AS5388.NET (195.92.169.3) 2239.281 ms 2322.246 ms 1158.991 ms
4 BNR-1.TCL.AS5388.NET (195.92.201.153) 118.801 ms 2461.639 ms *
5 BNR-2.TCL.AS5388.NET (195.92.200.195) 2739.316 ms 2634.588 ms *
6 pomegranate.AS5388.NET (195.92.201.13) 2100.165 ms 1577.329 ms *
7 linx.london.above.net (195.66.224.76) 2729.521 ms * *
8 lga1-lhr1-stm4.lga1.above.net (208.184.231.21) 196.944 ms 2450.044 ms *
9 * * iad1-lga1-oc192-2.iad1.above.net (208.184.233.61) 1339.991 ms
10 core1-core4-oc48.iad1.above.net (208.185.0.137) 2061.354 ms * 219.314 ms
11 sjc2-iad1-oc48.sjc2.above.net (216.200.127.26) 270.791 ms 1069.196 ms *
12 sfo1-sjc2-oc48-2.sfo1.above.net (208.184.232.54) 889.482 ms 2820.425 ms *
13 main1colo78-core1-oc48.sfo1.above.net (208.184.228.2) 1910.051 ms 2318.183 ms
1878.781 ms
14 above-gw.sfo1.collab.net (209.133.67.29) 2088.998 ms * 1759.875 ms
15 * * cr1-ge2-2-sfo.collab.net (64.125.132.9) 2269.453 ms
16 d2r1-ge2-1-sfo.collab.net (64.125.132.46) 2348.632 ms * 315.531 ms
17 64.125.132.231 (64.125.132.231) 284.888 ms 1204.667 ms 909.628 ms
