Go to the first, previous, next, last section, table of contents.
First you need to create system accounts that would own your repository.
It is not discussed here exactly how to do that, because the methods
vary from system to system. Only the suggested names and purpose of
those accounts is discussed. You will need the following groups and
accounts:
- `cvsadmin' account
-
This account will own the repository directory itself, and the
`CVSROOT/' subdirectory.
This account has the `cvsadmin' group as its primary group, and
additionally belongs to the `cvs' group.
- `cvsadmin' group
-
This group will own the `CVSROOT/' subdirectory in the repository,
and all of its contents.
- `cvs' account
-
This account owns two files: `CVSROOT/history' and
`CVSROOT/val-tags', and also all subdirectories except for the
`CVSROOT/' (and files in them) will belong to this account.
This account has the `cvs' group as its primary group.
- `cvs' group
-
This group will own the repository directory itself, every subdirectory
except for the `CVSROOT/', and all the files in those
subdirectories. No system accounts that belong to real users
should ever be in the `cvs' group. Only the `cvsadmin' and
`cvs' accounts should be in this group.
Note that the two accounts and two groups mentioned above are used for a
single repository. If you're hosting several virtual repositories on a
single machine, you will have to create two accounts and two groups for
each of those repositories. Suppose you have a repository in
`/repos1'. Create, for example, `repos1cvs' and
`repos1admin' accounts and groups, for this repository. Later on
we will use generic `cvs' and `cvsadmin' names.
Go to the first, previous, next, last section, table of contents.