François Revol wrote on Sat, 28 Jun 2003 01:31:26 +0200 (CEST): > Seems to be a transcient error... > SF.net warned they would use a 1-day old copy for anon cvs, but they > didn't say it would fail :^) They did say that their load balancer would cut the anonymous CVS connection (pserver-based CVS access) if their system was too busy, and that you'd get an EOF error when that happens. From the site status page: (2003-06-19 04:50:08) Developer CVS performance (via SSH) has stabilized at a reasonable level. pserver-based CVS access continues to be served off of the CVS backup server. As of the morning of 2003-06-19, the connection count for pserver connections has been raised as to permit a larger volume of pserver connections at a time (this connection cap exists to help us balance the volume of pserver connections at peak times with the performance of those connections). pserver-based repository access from the project shell server will continue to operate as stated in our previous update (against data on the primary CVS server). Users encountering the connection cap (please note that this ONLY applies to pserver-based CVS access and DOES NOT deal with SSH-based CVS access) will receive either a recv() error or an "end of file from server" error. Users encountering this cap should wait a few minutes, then retry their connection. The increased connection cap established on 2003-06-19 is expected to alleviate most of these issues. Project administrators are encouraged to establish custom nightly CVS tarballs (i.e. that contain a working source snapshot that their non-member developers may download) for their project if they believe the connection counts are continuing to impact their development cycle (note that these connection counts will only impact non-member developers, since member developers may use SSH authentication instead of pserver). The SourceForge.net team will be glad to assist project administrators in establishing a custom nightly snapshot tarball for their project when requested by Support Request after 2003-06-19 (the increased connection cap established on 2003-06-19 is expected to alleviate most of these issues). - Alex