2009-06-06 07:32 AEST by Arthur Barrett - If cvsdiag determines that this PC has at least 1 readable repository and is running cvsservice/cvsloc 
then cvsdiag could run 'non-destructive' tests and display success/fail results.

For all 'local' repositories the cvsdiag could run some 'tests':
cd %TEMP%
* cvs logout
* cvs info -r hostname
* cvs info -b
* cvs rls
* cvs rls pick-a-name-from-previous-result
* cvs rlog
* cvs checkout -d cvsdiag pick-a-name-from-rls-result
* cd cvsdiag
* cvs status
* cvs editors
* cd ..
* rm -rf cvsdiag



The cvsdiag would need to have some 'timeout' enabled and if any command failed to respond/close 
within the timeout period then it should abort cleanly.

Since cvsdiag is clearly on the server it could set ServerTraceFile, and if any command failed it could 
include that information.


A secondary 'destructive' test could be a c/c++ version of 'testcvs' that uses first :local: then :sspi.  It 
would first need to create a new repository (which testcvs already does) but first checking that the 
repository name was not already in use, and maybe even prompting to confirm the 'location'...