RE: how to prevent cvs from locking?

[Wiest, Damian]

> -----Original Message-----
> From: Jim Hyslop [mailto:address@hidden 
> Sent: Thursday, September 22, 2005 12:31 PM
> Cc: address@hidden
> Subject: Re: how to prevent cvs from locking?
> 
> 
> 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.
> 
> > using rhel 3
> > 
> > we do not want cvs to create any lock files.
> 
> Yes, you do. Otherwise your repository *will* get corrupted.
> 
> > 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.
> 
> 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?
> 
> -- 
> Jim

I should probably check out the code before I mention this, but I don't
believe cvs installs signal handlers to properly cleanup temporary files;
for example, sending cvs SIGINT during certain operations will leave behind
files.  I'm not sure if the lack of signal handling is intentional or not.

I'm wondering if the original poster would be better off with rcs versus
cvs?

-Damian