[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: intermittent cvs lock messages

From: Todd Denniston
Subject: Re: intermittent cvs lock messages
Date: Thu, 26 May 2005 09:43:34 -0500

Sam Steingold wrote:
> Hi,
> I use
> "Concurrent Versions System (CVS) 1.11.17 (client/server)"
> via SSH on cygwin and linux.
> During CVS commit, I often get this messages:
> Message: [22:06:14] waiting for sds's lock in /cvsroot/clisp/clisp/tests
> [note, "sds" is myself]
> then, after a few minutes, commit succeeds.

two possibilities I can think of:
1) you are doing some other cvs operation at the same time. (which
version(s) of CVS or/and CVS GUI/SSH agent/SSH clients are you using? or
perhaps you use a script to do your commit, and it starts the secondary work
too soon?)
2) the project admins have put some kind of automatic tool in the committing
script that does a cvs operation in your name. (you may have to ask the
Project admins.)

> I reported this to the repository maintainers and they said that there
> are no lock files there:
> <>

Compared with your notes here and in that bug report, their analysis seems
You indicate the commit goes on, after a while, so the locks are definitely
not there by the time they looked for them.

> it appears that the locks are created by my client during commit:
> when I commit "foo", it locks "foo" and then tries to commit it and
> runs into its own lock (which it then reports back to me in the above
> message), and, after waiting for the lock to expire (in a few minutes),
> it proceeds with the commit.
> is this really the case?
> Thanks!

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]