Problems accessing CVS tree

Problems accessing CVS tree

[Richard Kenner]

I'm still seeing the problem below.  When is this scheduled to be fixd?

19  p9-0-0.paloalto-br2.bbnplanet.net (4.0.2.198)  172 ms  164 ms  172 ms
20  f1-0.paloalto-cr20.bbnplanet.net (131.119.4.2)  276 ms  152 ms  126 ms
21  s0.cygnus3.bbnplanet.net (4.1.120.86)  324 ms  289 ms  194 ms
22  sourceware.cygnus.com (205.180.83.71)  282 ms  276 ms  326 ms

Re: Problems accessing CVS tree

[Eric Christopher]

Richard Kenner wrote:
> 
> I'm still seeing the problem below.  When is this scheduled to be fixd?
> 
> 19  p9-0-0.paloalto-br2.bbnplanet.net (4.0.2.198)  172 ms  164 ms  172 ms
> 20  f1-0.paloalto-cr20.bbnplanet.net (131.119.4.2)  276 ms  152 ms  126 ms
> 21  s0.cygnus3.bbnplanet.net (4.1.120.86)  324 ms  289 ms  194 ms
> 22  sourceware.cygnus.com (205.180.83.71)  282 ms  276 ms  326 ms

There have apparently been intermittent problems on the west coast in
general the last few days.  My connect time is slightly better:

 9  f1-0.paloalto-cr20.bbnplanet.net (131.119.4.2)  4.571 ms  7.024 ms 
7.549 ms
10 s0.cygnus3.bbnplanet.net (4.1.120.86)  149.677 ms  187.668 ms 
105.756 ms
11  sourceware.cygnus.com (205.180.83.71)  113.702 ms  148.927 ms 
207.253 ms

-eric

Re: Problems accessing CVS tree

[Gerald Pfeifer]

On Sat, 15 Jul 2000, Richard Kenner wrote:
> I'm still seeing the problem below.  When is this scheduled to be fixd?
> 
> 19  p9-0-0.paloalto-br2.bbnplanet.net (4.0.2.198)  172 ms  164 ms  172 ms
> 20  f1-0.paloalto-cr20.bbnplanet.net (131.119.4.2)  276 ms  152 ms  126 ms
> 21  s0.cygnus3.bbnplanet.net (4.1.120.86)  324 ms  289 ms  194 ms
> 22  sourceware.cygnus.com (205.180.83.71)  282 ms  276 ms  326 ms

I'm seeing similiar ping times/traceroutes from here (Austria, Europe),
but this is not a problem for me: A full `cvs update` is way below one
minute, for example.

As for being fixed, the problem most likely is the T1 to sourceware being
saturated by FTP traffic for GCC and Cygwin.

The Cygwin folks already reduced the frequency of snapshots (every three
days now, daily before) and for GCC I have removed all direct links to
snapshots and releases, referring to mirror sites instead.

What should be done, however, is to also update the snapshot script to do
the same (and possibly give the mirrors a chance to pick up the snapshot
before sending the announcement).

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
Have a look at http://petition.eurolinux.org -- it's not about Linux, btw!