[Top][All Lists]

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

RE: CVS Permissions

From: Arthur Barrett
Subject: RE: CVS Permissions
Date: Wed, 18 Aug 2004 16:51:32 +1000


I suppose you could view CVSNT as "3rd party" - but it's actually GPL, GNU, 
completely open source and free.  

It is the "standard cvs" bundled with WinCVS and TortoiseCVS etc, and has been 
for a long time.

CVSNT is an active project with regular feature releases for over 6 years.


Arthur Barrett

-----Original Message-----
From:   Gaurav Vaish [mailto:address@hidden
Sent:   Wed 8/18/2004 4:25 PM
To:     Arthur Barrett
Cc:     address@hidden
Subject:        Re: CVS Permissions

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.


On Tue, 17 Aug 2004 17:51:29 +1000, Arthur Barrett
<address@hidden> 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:
> Regards,
> Arthur Barrett
> -----Original Message-----
> From:   address@hidden on behalf of Gaurav Vaish
> Sent:   Tue 8/17/2004 3:46 PM
> To:     address@hidden
> 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
> -----------------------------

reply via email to

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