cvs server: waiting for anoncvs's lock in /cvs/src/src/gdb

cvs server: waiting for anoncvs's lock in /cvs/src/src/gdb

[Eli Zaretskii]

Is there any reasonable way to prevent anoncvs from locking the 
repository for prolonged periods of time?  I've just committed a small 
change, and now I'm sitting before the terminal for 30 minutes staring at 
``waiting for anoncvs's lock'' messages.  And it's not over yet.

This is ridiculous: anoncvs access to the GDB sources should not punish 
the developers so much!

Is this a CVS limitation, or can something be done?

Re: cvs server: waiting for anoncvs's lock in /cvs/src/src/gdb

[Eli Zaretskii]

On Thu, 3 May 2001, I wrote:

> Is there any reasonable way to prevent anoncvs from locking the 
> repository for prolonged periods of time?  I've just committed a small 
> change, and now I'm sitting before the terminal for 30 minutes staring at 
> ``waiting for anoncvs's lock'' messages.  And it's not over yet.

After waiting for more than an hour, I gave up and typed Ctrl-C.

This shouldn't happen.

Re: cvs server: waiting for anoncvs's lock in /cvs/src/src/gdb

[Jonathan Larmour]

In article < Pine.SUN.3.91.1010503140324.613J-100000@is > you write:
>Is there any reasonable way to prevent anoncvs from locking the 
>repository for prolonged periods of time?  I've just committed a small 
>change, and now I'm sitting before the terminal for 30 minutes staring at 
>``waiting for anoncvs's lock'' messages.  And it's not over yet.
>
>This is ridiculous: anoncvs access to the GDB sources should not punish 
>the developers so much!
>
>Is this a CVS limitation, or can something be done?

It was a stale lock. The cvs server instance that created it must
have crashed.

I've deleted it so it should work now.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: cvs server: waiting for anoncvs's lock in /cvs/src/src/gdb

[Eli Zaretskii]

On Thu, 3 May 2001, Jonathan Larmour wrote:

> It was a stale lock. The cvs server instance that created it must
> have crashed.
> 
> I've deleted it so it should work now.

Thanks.

If and when this happens, who should I tell about that, and ask to remove 
the lock?

Re: cvs server: waiting for anoncvs's lock in /cvs/src/src/gdb

[Christopher Faylor]

On Thu, May 03, 2001 at 04:28:40PM +0300, Eli Zaretskii wrote:
>
>On Thu, 3 May 2001, Jonathan Larmour wrote:
>
>> It was a stale lock. The cvs server instance that created it must
>> have crashed.
>> 
>> I've deleted it so it should work now.
>
>Thanks.
>
>If and when this happens, who should I tell about that, and ask to remove 
>the lock?

overseers@sources.redhat.com is the right place.  People with root access
read this mailing list.

If you send something here, though, I'll read it eventually and deal
with it.  I was busy today or I would have gotten to it sooner.

Thanks to Jonathan for his action, though.

cgf

Re: cvs server: waiting for anoncvs's lock in /cvs/src/src/gdb

[Philip Blundell]

>Is there any reasonable way to prevent anoncvs from locking the 
>repository for prolonged periods of time?  I've just committed a small 
>change, and now I'm sitting before the terminal for 30 minutes staring at 
>``waiting for anoncvs's lock'' messages.  And it's not over yet.

If you were stuck for this long, it almost certainly means a CVS process has 
died and left a stale lock in the repository.  Someone needs to go in and 
delete it manually.

The problem isn't specific to anonymous access; that's not to say it mightn't 
be a good thing to get anoncvs out of the main repository and on to some kind 
of mirror.

p.