The Ur-Quan Masters Discussion Forum

The Ur-Quan Masters Re-Release => Technical Issues => Topic started by: Sage on July 29, 2003, 03:39:52 pm

Title: CVS Login Problem
Post by: Sage on July 29, 2003, 03:39:52 pm
I can't seem to access the CVS tree using the anonymous login. It seems like it's rejecting the password (none being put in, mind you). Here is what I get in the command line...

D:\Documents and Settings\Sage\My Documents\uqm>cvs login
Logging in to
CVS password:
cvs [login aborted]: end of file from server (consult above messages if any)

No error messages, and thus nothing to consult. Anyone else having this problem or willing to hand over the latest source?

EDIT: I also tried working from a different directory entirely (root of C: and also C:\uqm\), and got this error message after putting in a (lack of a) password.

cvs [login aborted]: could not find out home directory

Title: Re: CVS Login Problem
Post by: Nic. on July 29, 2003, 07:26:17 pm
Oh, what a glorious time to be alive.  You're running into two similar problems, one of which is trivial (but annoying), and the other is severe (but not your fault, and out of your control)

The first is that win32 CVS is extremely flaky when it comes to "bootstrapping" itself into cognisance.  You'll need to run "cvs login" two or three times until it gets all of its config files written to disk; after that it should report no errors, which means you are all set.

The second problem is that there is a "connection cap" on anonymous CVS sessions at SourceForge, the host of the UQM project.  If too many concurrent users try to update their CVS trees, the server will (somewhat discriminately) start dropping connections to keep the performance at an acceptable level.  The only thing you can do is try, try again; eventually you'll get through, but it's an ugly hack that needs to go away.  On the bright side, my employer ( produces a software product that would effectively eliminate their CVS scaling issues, but we'll not have a chance to talk with them about it until after the LinuxWorld conference next week.  When you factor in the time for them to test/integrate if they do decide to use our product, SourceForge CVS is going to be all but unusable for the next few months at least.  Yay.

Title: Re: CVS Login Problem
Post by: Culture20 on July 31, 2003, 01:20:25 am
Dear User,

In my last email to you, I mentioned that the biggest issue with the
running of the site is managing our growth.  Adding 700 new users and 70
new Open Source projects a day can, at times, create strain on
critical systems that drive the site.

As you may have noticed, CVS is visibly having growing pains.  Due to
system load, we have had to move anonymous checkouts to our backup
server.  This has made the code of our 65,000 projects more
accessible.  However, since data is synchronized from the primary
CVS servers to the backup CVS servers at specific times during the day,
it has also caused up to a 24 hour delay in getting the
freshest code on the site.

I know this temporary solution has frustrated some of you and I want
to apologize for that.

The good news is, in the very short term, we will have a solution
that will solve this issue.  We are upgrading our hardware from one
aging system to six new speedy boxes; this hardware is a portion of the
new CVS infrastructure that we are implementing to improve CVS
performance and reliability.

The solution will be in place by the time I write you next month.
You'll know when we make the change.  It will be hard to miss.  In the
mean time, hang in there.  I know it's frustrating, but help is on the

As always, if you have some feedback or issues related to the site,
please feel free to email me directly at

Patrick McGovern

From an email dated July 27, 2003

I doubt anything will come of suggestions sent to his address, but you could always try...

Title: Re: CVS Login Problem
Post by: Culture20 on July 31, 2003, 01:26:02 am
If it's any consolation Sage, it takes me about 50-70 attempts before I get a checkout or update from SF lately.  Many of us run the commands in scripts which repeatedly attempt to update until the first success.  This, unfortunately has the effect of flooding SF's cvs server with requests (unless you tell your script to pause between attempts), preventing regular folk who type the commands by hand from ever getting in.

Title: Re: CVS Login Problem
Post by: Sage on July 31, 2003, 05:32:25 am
Making a script shouldn't be too hard. I suppose that's worth a shot then. Maybe I'll be logged in sometime tomorrow if I keep trying at it, eh?