[cvsnt] Problems setting up a repository

[Bo Berglund]

You have set it up erroneously....

The Repository prefix is meant to point at a folder where the CVSNT served repositories *start*.
You have set the prefix to D:/CVS so this means that all the repositories you create will live in this folder.
Each repository is a folder in itself so you cannot specify /. as the root, that is the same as the prefix and it is invalid.

The correct setup would be (for two repositories and 5 modules):
D:/CVS/REPO1
        |-CVSROOT
        |-Module1
        |-Module2
        |-Module3
D:/CVS/REPO2
        |-CVSROOT
        |-ModuleA
        |-ModuleB


/Bo

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Moore, Paul
Sent: den 11 mars 2004 16:07
To: CVSNT (E-mail)
Subject: [cvsnt] Problems setting up a repository


I'm trying to set up a CVSNT repository on a Windows 2000 server. I know very little about Windows security, which is probably why I'm having problems :-(

Both my PC and the server are in the uk.int.atosorigin domain. My user ID is in the UKAO domain. Actually, I suspect this is all active directory, but as I say, I know very little in this area. I installed CVSNT on the server, and created a directory D:\CVS. I set the repository prefix to D:/CVS, and added a repository root of /. The applet told me that it wasn't a valid repository, and did I want to initialise it. I said yes, and the D:/CVS/CVSROOT directory was set up.

However, on my PC, I now get

>cvs -d :sspi:ukdcr030:/ ls
cvs [ls aborted]: No valid repository roots defined.  Aborting.

I've tried setting permissions on the directories, basically letting people have full access (security isn't a major issue here), all to no avail. Using a local connection on the server everything looks OK.

>cvs -d :local:D:/CVS ls
Listing modules on server

CVSROOT

But the sspi protocol fails on the server as well as from my client.

Can anyone suggest anything I might be doing wrong? It may well be something really dumb - I went with the idea that doing a default install and taking as many defaults as I could manage, would get me going. And indeed it did on my standalone PC at home. I suspect it's to do with something about our network setup (the server is on the "servers" part of our network, and the client on the "internal clients" part, but I don't know much about what that implies in practice). Any pointers on what to look for would be much appreciated...

Thanks,
Paul
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt