So, does that mean the permission issue is a standard problem?

I would be surprised then! There must be someway to overcome this in
the default CVS server itself, rather than going for 3rd party
implementation of the CVS, like CVSNT you mentioned.



Cheers,
Gaurav
http://iitk.mastergaurav.net
-----------------------------


On Tue, 17 Aug 2004 17:51:29 +1000, Arthur Barrett
<[EMAIL PROTECTED]> wrote:
> Gaurav,
> 
> CVSNT (also open source - also runs on Linux) solves this problem by using a 
> separate lock server.
> 
> You can download source and binaries for Linux here:
> http://march-hare.com/cvspro
> 
> Regards,
> 
> Arthur Barrett
> 
> 
> 
> 
> -----Original Message-----
> From:   [EMAIL PROTECTED] on behalf of Gaurav Vaish
> Sent:   Tue 8/17/2004 3:46 PM
> To:     [EMAIL PROTECTED]
> Cc:
> Subject:        CVS Permissions
> 
> Hi,
> 
>  I setup CVS on a Linux machine and I'm facing problem with permissions.
> 
>  I am using pserver to connect and more often than not, I get the
> error - "Unable to create #cvs.lock, Permission denied".
> 
>  The reason is that a module or a subdirectory thereof will be
> created by the permission set of the permission who created it. Though
> the directory permissions are 775 and all the users are in the group
> "cvs", but still the problem persists.
> 
>  Even during checkout, I get this error. I have to logon to the
> server and change the permissions to cvs.cvs whole of the hierarchy.
> "chown -R" is a big pain.
> 
>  Any help in this direction will be welcome.
> 
> Cheers,
> Gaurav
> http://iitk.mastergaurav.net
> -----------------------------


_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

Reply via email to