SF corpsed?

[Robin Becker]

In article <39EFC5E2.86A0E0C9 at ajubasolutions.com>, Jeffrey Hobbs
<jeffrey.hobbs at ajubasolutions.com> writes
...
>login as in ssh?  That works for me, as does cvs:
>
>pop [~/cvs/tkcon] 5 % tkconcvs up
>hobbs at cvs.sourceforge.net's password:
>cvs server: Updating .
>cvs server: Updating docs
>cvs server: Updating extra
>
>(tkconcvs is just an alias to get the right cvs tree).  It looks
>like you may have a cvsroot problem.  Checking their support manager
>entries for recent entries:
>http://sourceforge.net/support/?func=browse&group_id=1&set=open&offset=50
>
>I see that there are numerous similar problems already noted.  Perhaps
>anyone doing cvs activity during some burp in the system got hosed.
>I'd submit a support request for your project as well.
>
I always used ssh for sf, but that won't help with cvs locks as far as I
can tell as the only people who can remove the #locks are sf people.
It's all come back now so it was some kind of global problem.

Makes you wonder if the one strategy is non-robust argument may not be
true after all.
-- 
Robin Becker