This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Creating a tag
- From: law at redhat dot com
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 19 Jun 2002 13:52:48 -0600
- Subject: Re: Creating a tag
- Reply-to: law at redhat dot com
In message <120100000.1024515506@warlock.codesourcery.com>, Mark Mitchell write
s:
>
> > > cvs server: [09:08:08] waiting for sje's lock in /cvs/gcc/gcc/gcc
> > > cvs server: [09:15:39] waiting for anoncvs's lock in /cvs/gcc/gcc/gcc
> > > cvs server: [10:27:37] waiting for rth's lock in /cvs/gcc/gcc/gcc
> > > cvs server: [10:41:30] waiting for anoncvs's lock in /cvs/gcc/gcc/gcc
> > > cvs server: [10:45:01] waiting for rth's lock in /cvs/gcc/gcc/gcc
>
> > Presumably there were other directories interlaced with these?
>
> Right.
Well, maybe it was trying to get a lock on the repo as a whole. I'm certainly
not an expert on the inner workings of CVS.
> I'm not sure there's anything we can do, other than the faster machine.
That's really the solution. The current machine is already beyond it's
expected lifetime (2 years). The problem is finding the time to get the
new box set up.
> (I had hoped that I was doing something idiotic, and that by manipulating
> CVS more intelligently I could have made progress more quickly, but it
> sounds like the system, and not I, is to blame.)
I think you're simply running into the limitations of the current hardware
with its current service load.
jeff