BJ> Thanks for the note.  Turns out I was getting bit by SourceForge's 
 BJ> split of cvs activity between the primary and 
 BJ> backup CVS server.  For 
 BJ> some reason, I still can only access the primary CVS server if I 
 BJ> specify a long command line option (using -d).  Otherwise, I end up 
 BJ> on the (default) backup CVS server, that is read-only and contains 
 BJ> data up to 24 hours old.  :(

 BS> Maybe it's CVSROOT=... or CVS_ROOT=... i really can't 
 BS> remember, longtime since i have been using CVS.

Hmmm....  Now I'll have to double check the sourceforge documentation I was
reedting to see if I read thru CVS_ROOT as CVSROOT.....

 BS>> Should be
 BS>> CVSROOT=:pserver:{at}cvs.sourceforge.net:/cvsroot/maximus 

 BJ> This still will only (default) to using the backup sourceforge CVS 
 BJ> server, which is a read-only server.

 BS> Ok.. but did you fix it out?

Yes....

Funny thing is, the sourceforge documentation substitutes ext for pserver
for developer access.  Works when I use the -d commandline argument, but
runs the same when used in CVSROOT environment variable......

Strange....

Any way....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01