[Top][All Lists]

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

Re: how to prevent cvs from locking?

From: DC
Subject: Re: how to prevent cvs from locking?
Date: Thu, 22 Sep 2005 14:18:43 -0400

On Thu, 22 Sep 2005 13:30:59 -0400, Jim Hyslop <address@hidden> wrote:

>DC <address@hidden> wrote:
>First of all, please do not make up email addresses. If you're concerned 
>about spam, create a throw-away gmail or hotmail address, then abandon 
>it one your concerns have been answered.

I would rather put a non-existant email address out there, then one that im 
never going to look at. At least they might get a bounce back if
it dosn't exist.  But, for the sake of newsgroup postings, I have created a 
gmail account.

>> using rhel 3
>> we do not want cvs to create any lock files.
>Yes, you do. Otherwise your repository *will* get corrupted.

it is a very small group of developers. Most of the time they will be in 
completely different places on the branch. For the most part people
don't touch each others files, and when they do there is usually a discussion 
of how/what/what/etc before hand.

If it were my descision I would set this up so that people create files as 
username:cvspub rather then cvspub:cvspub. I would also make it
so that two people could not checkout the same file at the same time. However, 
this is not my decision :(

>> this has been working for a while, but the last two users that we added are 
>> all creating lock
>> files, and it is preventing them from being able to update, or do anything 
>> else for that matter.
>You're looking at this the wrong way around. The problem is not that the 
>lock files exist. CVS automatically creates them and cleans them up, and 
>has been all along. You just haven't noticed it until now.
>Your real problem is, something is preventing CVS from cleaning up the 
>lock files when it's done.

Ok, that sounds perfectly logical. However why would this start happening for 
one user, and not anyone else. We are all using the same

>What version of the client and server are you using? Can you 
>consistently reproduce the problem? Exactly what command sequence 
>reproduces the problem, and exactly what error message are you getting?

Server: RHEL3 
running cvs-1.11.2-28. (This is what Redhat is calling up to date. I tried 
downloading the RHEL4 update cvs-1.11.17  but couldn't get it to
rpmbuild correctly.)

Client: TortoiseCVS 1.8.21

Command tortoise is attempting:
"C:\Program Files\TortoiseCVS\cvs.exe" "-q" "update" "-d" "-P" 

cvs: rcs.c:4114: RCS_checkout: Assertion `rev == ((void *)0) || 
((*__ctype_b_loc ())[(int) (((unsigned char) *rev))] & (unsigned short int)
_ISdigit)' failed. 
Terminated with fatal signal 11 
Error, CVS operation failed 

reply via email to

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