Re: stale cvs lock in src/gdb

[Tristan Gingold <gingold at adacore dot com>]

On Feb 16, 2012, at 4:54 PM, Ian Lance Taylor wrote:

> Tristan Gingold <gingold@adacore.com> writes:
> 
>> looks like there is a stale lock:
>> 
>> …
>> cvs commit: [12:39:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:39:40] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:40:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:40:40] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:41:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:41:40] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:42:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:42:40] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:43:10] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:43:41] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:44:11] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:44:41] waiting for anoncvs's lock in /cvs/src/src/gdb
>> cvs commit: [12:45:12] waiting for anoncvs's lock in /cvs/src/src/gdb
> 
> Stale CVS locks are rare, because the locks include a PID, and if the
> PID does not exist the lock is automatically broken.  I suspect this was
> an anonymous CVS checkout over a slow network link.  In any case I don't
> see any lock there now.  Let us know if you are still having trouble.

Thanks.  It has been fixed.  Maybe it was a very very slow checkout as it was stale for several hours.

Tristan.