[cvsnt] CVSNT on real server environment

Bo Berglund Bo.Berglund at system3r.se
Thu Nov 13 11:05:57 GMT 2003

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

This is old knowledge...
The Temp folder CVSNT uses MUST be world writeable.
Using %systemroot%\Temp is no good because of Microsoft changes:

In NT4 this permission was the default and so it works
In W2000 this is also the case
In XP and up this is forbidden and so CVSNT cannot use this temp dir

The best way (and spelled out in my installation tips) is to create
a Temp folder completely in a different location and set the permissions
to Everyone Full Control on this folder, then use this as the CVSNT
Temp folder.

Also you should enable the lockserver usage by checking out CVSROOT and
uncommenting the Lockserver line and then check it back in again.
This removes the need for writing locks into the repository itself too.
The Temp folder is still needed as intermediate file storage during commits
I believe.


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Mike
Sent: den 13 november 2003 11:54
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] CVSNT on real server environment

A often encountered problem using CVSNT is "cannot find.: No such file or
directory" when impersonation is enabled. This is mainly true using
Eclipse as a CVS client. The eclipse staff just tell that this is an
incompatibility of CVSNT. The simplest solution to this problem is to
disable impersonation on CVSNT and additionally remove all access
restrictions from the CVS (root) directories. But so no user access
management can be established.

The real problem is that CVSNT uses a temporary directory (default is
%SystemRoot%\temp) and every user must have write permissions to this
directory too, but on a real server ordinary users do not have this right.
So the solution is to set a different temporary directory that every user
of CVSNT can access.

Now it is possible to restrict the access rights of users on a directory
level, sothat nobody can read and/or change files which he is not
authorized to.

cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook