You may either download one of the releases, provided as source tarballs, from the cvsuser File List page or you may obtain cvsuser through anonymous cvs.
If you wish to download the latest development version via anonymous CVS, please follow the directions below. Please note that there is no guarantee
that what you download will work, or even compile.
From your working directory, type in the following at your shell's command prompt:
cvs -d :pserver:email@example.com:/cvsroot/cvsuser login
cvs -d :pserver:firstname.lastname@example.org:/cvsroot/cvsuser co cvsuser
At the "CVS password:" prompt, simply press Enter. You should now have a directory called "cvsuser" within your current working directory.
Note that releases available under CVS use the tags: Beta_0_20, Beta_0_10, Alpha_0_01
cvsuser is now built using the autotools and follows the same build and installation procedure as most free software packages. To build and install
cvsuser, perform the following steps.
cd cvsuser-0.20-beta (Or whatever directory cvsuser was installed under)
./configure --prefix=/usr --mandir=/usr/share/man
su -c "make install"
su -c "chmod 6550 /usr/bin/cvsuser"
su -c "chown cvsadmin /usr/bin/cvsuser"
su -c "chgrp cvsadmin /usr/bin/cvsuser"
su -c "chmod 6550 /usr/bin/cvsuserd"
su -c "chown cvsadmin /usr/bin/cvsuserd"
su -c "chgrp cvsadmin /usr/bin/cvsuserd"
When the system prompts for a password, enter the system's root password. Also note that the cvs username and groupname needs to be changed as needed
to match your system configuration. It is strongly suggested that cvsuserd not be configured suid root to minimize any security risks. For SuSE Linux and
Mandrake Linux, the configure line above should be optimal. On other distributions (such as Debian) this line may need to be changed accordingly.
On most systems providing remote administration of CVS password files, the cvsuserd daemon will need to be started during boot. Also note that cvsuserd
will generate and maintain a logfile at /var/log/cvsuserd.log. Permissions on this file may need to be adjusted to guarantee that the logfile can be
generated by the daemon.
Note that the file defaults.h in the top level directory contains most program configuration settings that might need to be changed
to suit your system configuration. In all but the rarest cases, no changes should be necessary.