[cvsnt] required access rights to the raw repository

Wed Nov 6 09:35:06 GMT 2002

> -----Original Message-----
> From: Bernhard Weichel [mailto:bernhard.weichel at online.de]
> Sent: 5. november 2002 21:01
> To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> Subject: Re: [cvsnt] required access rights to the raw repository
>
> 1. we have a fileserver in which I want to place the raw repository as
> well
> as a reference copy of the most recent version (for management which
has
> no
> sandbox). The file server is professionally backed up. So all project
data
> is maintained there. No application service is allowed on \\fs0007.
> 
>    \\fs007\myproject\CVS-repository\workproducts
> 
>    \\fs007\myproject\reference-copy
> 
> 2. we will have an application server (called myappsvr) on which we
will
> run
> the CVSNT service. The fileserver shares are mapped to drives there:
> 
>    r: is mapped to \\fs007\myproject\CVS-repository
> 
>    Repository prefix is set to r:/CVS-repository

This is a no-go.

It has been stated numerous times (by Tony Hoyle, the maintainer of
CVSNT) that the server must have direct access to the drives hosting the
repository due to the nature of CVS' file operations.
Using a network share is asking for trouble. Corruption of the RSC files
is the likely outcome over time. 

You must equip myappsvr with adequate disks and include it in the backup
circus.
There should be _no_ direct access to the drive holding the repository.

> 3. each developer has his sandbox, lets say on C:
> 
>    c:\myproject

That is a genuinely good idea :-)
Workspaces should always be on local not shared drives.

>    The project manager will perform CVS update on the reference-copy
on a
> regular basis (perhaps controlled by a scheduler.

This you can accomplish with CVSNTUpd hooked into loginfo.

> For this purpose, he will also map
> 
>    x: will be mapped to \\fs007\myproject\reference-copy
> 

Good Luck!
/anders