Providing customized source code control with CVS

The "history" file should be in the CVSROOT directory in the repository if the "cvs history" facility will be used. It needs to be world-writeable. It should be trimmed periodically, and the cvs_history_trim.pl Perl script is provided for that purpose.

If CVS jobs are interrupted, it is possible that files will eventually clutter up the "/tmp" directory on the server. For that purpose, the following command should be run daily as root (it will delete all files and directories that have not been touched for two days):
find /tmp -mtime 2 -exec rm -rf {} \;


These are best set up as cron jobs. To give a sample, become root and create a file named cvs.crontab with the lines
0 0 * * * /usr/bin/find /tmp -mtime 2 -exec rm -rf {} \;
10 0 1 * * /usr/local/bin/cvs_history_trim.pl
changing the /usr/bin/find and /usr/local/bin/cvs_history_trim.pl to whatever the absolute pathnames are on the system. (Keep track of where you put cvs_history_trim.pl, and type type find to find where "find" is.)

After doing that, type
crontab -u root cvs.crontab
and the first command will be run every midnight, and the second on the first of every month at ten minutes after midnight.

All contents of these pages Copyright 2002 by David H. Thornley.
Permission granted for verbatim copying and use within an organization.