[cvsnt] Re: cvs server: Permission denied

[Bo Berglund]

On Fri, 2 Dec 2005 16:00:18 -0500, "Qi, Xiaofeng" <xqi at indiana.edu>
wrote:

>Hi,
>We're currently using cvsnt 2.0.51.0 on a WindowsXP sp2 box, and running
>into problems of committing changes to the server.  The error message
>after issuing a cvs commit is as follows:
> 
>Checking in Control.cls;
>/cvsroot/src/AOControl/Control.cls,v  <--  Control.cls
>new revision: 1.17; previous revision: 1.16
>cvs server: cannot change mode of file
>/cvsroot/src/AOControl/Control.cls,v: Permission denied
>cvs [server aborted]: cannot rename file
>/cvsroot/src/AOControl/,Control.cls, to
>/cvsroot/src/AOControl/,Control.cls,: Permission denied
> 
>I searched the mailing list, and it looked like someone had run into the
>same problem before, but I couldn't find a posting that provides a
>solution.  Has anyone figured out what the problem is?  Your help is
>greatly appreciated.
> 

Open TaskManager on the CVSNT server.
Look for cvs.exe processes. These should not be there since a cvs
command lasts only a fraction of a second to a few seconds at the
most.
If you see cvs.exe there it means that at some time a commit operation
by someone has gone bad and the process has frozen on the server.
This locks the file by having the tempfile open and noone can do
anything with it...

Solution:
Kill all cvs.exe processes.

This can typically not be done from the TaskManager window since
SYSTEM owns the process, but using kill.exe from the resource kit will
do it.
I have a scheduled task that runs every night and kills any remaining
cvs.exe processes. After installing this we do not see these problems
anymore. We have an old 2.0.41 server in production so it is close to
yours.

If you don't see cvs.exe in TaskManager then you have another
problem...



/Bo
(Bo Berglund, developer in Sweden)