When working with a CVS Server, you can create triggers for (all or specific) CVS Repositories, which allows you to automate certain processes, such as updating a checked-out copy of the CVS Tree on the Server (or NFS/SMBFS share), or create an email-log of the transactions on the server (or specific repository).
This is a common practice for rapid development environments that utilize CVS, and is really a nice way to organize things, in my opinion.
mkdir -p /www/htdocs/projects
cvs co example
You should now have a checked-out copy of the repository 'example' in the '/www/htdocs/projects' directory. (e.g. /www/htdocs/projects/example/)
# file: /home/cvs/CVSROOT/loginfo
^example (date; cat; (sleep 2; cd /www/htdocs/projects; cvs -q update -d) &) 2> /www/htdocs/projects/cvs.error
If any errors occur, they will be logged to the '/www/htdocs/projects/cvs.error' file.
The purpose of this technique is to allow you to keep a 'live' synchronized checked-out copy of the CVS Tree, which is handy if your CVS Server and Web Server are running on the same machine, or sharing files via NFS/SMBFS, etc.