[Top][All Lists]

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

RE: cvs edit -c locked checkout problem

From: Krishnamoorthy, Balaji
Subject: RE: cvs edit -c locked checkout problem
Date: Wed, 24 Apr 2002 10:28:37 -0400

Could you please suggest where I can find the patch to make one user unable to 
unlock the lock of the other user . Is it a good idea to put such patches ? 
what would be the implications if I would put in that .


Balaji Krishnamoorthy
Senior Systems Analyst 
Architecture, IT
Standard & Poor's (S&P)
55 Water Street, 35th Floor
New York, NY 10041
Phone:  (212)-438-1118
Fax:       (212)-438-7482
Email:   address@hidden <mailto:address@hidden> 

-----Original Message-----
From: Robert J. Clark [mailto:address@hidden
Sent: Tuesday, April 23, 2002 7:36 PM
To: address@hidden
Cc: address@hidden
Subject: Re: cvs edit -c locked checkout problem

On Tue, 23 Apr 2002 14:44:22 -0400
"Krishnamoorthy, Balaji" <address@hidden>

> Hi All,
>     I have a CVS server setup in the Unix , all the users are defined
>     in the passwd file , of the repository . The CVSROOT is as 
>     ":cvspserver:address@hidden:/local/apps/cvs/sample
>     apprepository" .And these repositories are defined in cvsstart
>     file .
> The problem is 
> cvs edit -c for a locked checkout does not work. Any other user can
> unlock the file . 
> Could anyone please suggest a workaround .

Don't use CVS? The "C" in CVS stands for "Concurrent". This means that
anyone can edit any file at any time. If you need true locking, then you
will have to use one of the hacks floating around to add this to CVS or
live with the fact that CVS does not work that way.

- Rob

The information contained in this message is intended only for the recipient, 
may be privileged and confidential and protected from disclosure. If the reader 
of this message is not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, please be 
aware that any dissemination or copying of this communication is strictly 
prohibited. If you have received this communication in error, please 
immediately notify us by replying to the message and deleting it from your 

Thank you,
Standard & Poor's

reply via email to

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