[cvsnt] Strange problem with CVSNT and permissions
arthur.barrett at march-hare.com
Tue Aug 28 10:23:48 BST 2007
Please run cvsdiag on the server - it will report many things, but the important ones are whether it can write to the repository. Also try running commit with -ttt (cvs -ttt commit -m "") and look to see if there are any interesting messages in the log. In particular look for messages just before the error, and also at the top you will see it determine all the groups the user is a member of - check that engineering is one of those groups.
Finally check noone has set up any CVSNT ACLs, ie: check you are running ACLs in "compat" mode (check the CVSROOT/config file, should be aclmode=compat), and run cvs -d :pserver:server:/repo rlsacl .
From: cvsnt-bounces at cvsnt.org on behalf of Paul Whitfield
Sent: Tue 8/28/2007 4:49 PM
To: cvsnt at cvsnt.org
Subject: [cvsnt] Strange problem with CVSNT and permissions
Recently my place of work upgraded our network from a Novell server to a
windows 2003 server.
This caused our previously working cvsnt server to stop allowing
write access. (Previous to this the server had been running for
about 3 years).
All my attempts to fix this problem have been for naught.
Basically I have a permissions issue and I have not been able to resolve
The cvsnt is running on windows XP sp2.
The version of CVSNT is 2.5.03 Build 2382
(we had the same problem with a previous build of CVSNT,
so I upgraded to the most recent I could find ).
Read access to the server is working fine,
we have viewCVS setup and that is also working fine.
We are using sspi protocol, the CVS repo and temp directories
have full permissions enabled for a group called
Engineering and for myself and other test users
(who are in the engineering group).
(I can access the files via the network, see the expected permissions
and change read/write mode).
However, write access does not work. Any attempt to commit
a file does not work and the error
cvs [server aborted]: "commit" requires write access to the repository
Currently I have no writer file (although I have attempted adding one
which made no difference).
My configuration is as follows:
I am running a local lock server.
Run as user: client user
Default Domain: OMNITRONICS
Temp Directory: c:\cvstemp
Defaults for the lock server
Compatibility options : No flags ticked
Clients allowed to connect; Any CVS/CVSNT
All default plug ins installed
The SSPI had default settings
Advanced settings that are on
Lockserver listens locally only
Allow clients to trace server
I would greatly appreciate and tips or suggestions on What should I try
cvsnt mailing list
cvsnt at cvsnt.org
More information about the cvsnt