RE: "Stale" CVS locks

[Reinstein, Shlomo]

Hi,

Back to the network-mounted repository issue after a long time. See Larry's 
reply below. What is wrong with accessing a repository from Windows using 
":local:", when the repository is mapped to a drive letter (using Samba)?
Recently we get many problems of the form:
        cvs [tag aborted]: cannot rename file /..../,filename, to 
z:\...\filename,v: File exists
I assume this is because of the network-mounted repository, but I don't 
understand the reason for these problems. Can anyone explain this?

Also, do these problems never happen in a Linux client which accesses the 
repository with ":local:"?

Thanks,
Shlomo

-----Original Message-----
From: address@hidden [mailto:address@hidden
Sent: Tuesday, June 12, 2001 9:03 PM
To: address@hidden
Cc: address@hidden
Subject: Re: "Stale" CVS locks


> I'd like to know, is there a common way of handling these problems? If not,
> can you recommend us how to deal with this? If don't know if it matters for
> this problem, but we're using CVS (the same repository) from both Windows
> and Linux, and we're not using the client/server model of CVS (and we can't
> start using this model now). The Ctrl+Break case may perhaps be solved by
> capturing those keystrokes, but there may be other reasons for stale CVS
> locks such as when a machine crashes, so I think this problem should be
> solved more generally.

The problem occurs so rarely in practice (at least on Unix-like systems)
that removing the stale locks manually has been a perfectly reasonable
way to address the problem.  It sounds like you're using a network-
mounted repository (Samba?), which is practically begging for trouble,
so you shouldn't be surprised that you're finding it.  You really should
switch to client/server CVS -- why do you say you can't?

-Larry Jones

Hello, local Navy recruitment office?  Yes, this is an emergency... -- Calvin