Bo:

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

 BS> Jul 25 11:42 03, Bob Jones wrote to Bo Simonson:
 BS>                                              ^- My name is Simons_e_n :-)

Appologies, and thanks.  :(    I think I've started to type your name right
when I have to enter it.....    In Netmail, the nodelist lookup helps me
keep it correct.  In echo mail, I don't get that feature.  :(  Spelling is
my achileas (sp?) heal....  I'm usually consistant in my (mis)spelling, so
we shall see if I've got your name "programmed" in my memory
correctly at some point in the future....  [Now, I *thought* I double
checked the name for spelling when I entered it.  :(                  ]
 
 BJ> I'm seeing 'cvs : CVSROOT "" must be an
absolute pathname' 
 BJ> and 
 BJ> 'cvs : warning: skipping invalid entry in password file at 
 BJ> line 1' as error messages while using CVS with sourceforge.  

 BS> Oh you shouldn't care about that.

Something I did finally solved that one.....  Ah, I edited out an entry in
~/.cvspass that I erroneously created when I first tried to use CVS on that
account / box.

 BJ> I've got CVSROOT defined as:

 BJ> CVSROOT=:psserver:{at}cvs.maximus.sourceforge.net:/cvsroot/max
 BJ> imus

 BJ> where  is my sourceforge username.....

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

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

 BJ> Am I missing a parameter that I didn't catch out of other 
 BJ> discussions?

 BJ> I'm running with ssh 2 generated keys.

 BJ> CVS_RSH=ssh

 BJ> is in my shell environment.

 BJ> Comments?

 BS> Afair does sourceforge requrie that you put your keys 
 BS> into them, go into your profile thing on sourceforge 
 BS> there is the possiblity.

That's what I used, and takes 6 hours to migrate ones SSH keys to all of
the sourceforge machines.....  Based on testing, this part was and is
working fine.

Thanks for the thoughts.

Take care.....

Bob Jones, 1:343/41

--- Maximus/2 3.01