RE: F-ssh and cvs checkout - cannot start server via rsh

[Bill Biessman]

you're welcome.

I was surprised when it didn't work for you the first time.  I slap my
forehead each time I forget to fix it when I set up a new client.  That's
the ONE thing I DO know how to fix now.

bill

-----Original Message-----
From: Ning Zhu [mailto:address@hidden
Sent: Monday, June 11, 2001 11:33 AM
To: address@hidden
Subject: RE: F-ssh and cvs checkout - cannot start server via rsh


Bill,

Just want to let you know that your suggestion worked.  I probably did
something wrong last time.  Removing the double quote did resolve the TCL
problem.

Again, thanks very much!
N.


-----Original Message-----
From: Bill Biessman [mailto:address@hidden
Sent: Thursday, June 07, 2001 8:11 PM
To: address@hidden
Subject: RE: F-ssh and cvs checkout - cannot start server via rsh


I found a problem with the tcl install:  The windows path variable does not
get set properly.

If you go to right-click on My Computer, select Advanced, then Environment,
you will see a bunch of variable definitions in the bottom of the box.
Select the path variable (note that the exact procedure for getting to the
path variable is slightly different for NT or 2000).  Scroll left and right
untill you see the path for tcl.  In several of the installations I have run
into the path was correctly added except for the fact that it was enclosed
in double quotes.  e.g. "d:/tools/tcl/bin".  I found if I deleted the
double-quotes the tcl was found properly by wincvs.  The only problem I
imagine you would find would be caused if one of the directories in the path
to tcl had a white space in it.  This would segment the path variable.  I
think this is the reason the quotes were put in there in the first place.

good luck

bill

-----Original Message-----
From: address@hidden [mailto:address@hidden Behalf Of
Ning Zhu
Sent: Thursday, June 07, 2001 5:04 PM
To:
Subject: F-ssh and cvs checkout - cannot start server via rsh





Hello,

I have just downloaded WinCvs 1.2 and installed it on my Windows 2000 box.
Whenever I start up WinCvs, I get "TCL is *not* available, shell is
disabled".  It seems that TCL is needed in order for WinCvs micros to work.
So I downloaded an ActiveTcl 8.3.3 package from the link that cvsgui.org
points to and installed it on the same box (cvs client).  It didn't resolve
the problem.

Also, I am using F-SSH to connect to our remote machine which forwards its
connection to a real CVS server.  I have my CVSROOT set to
":pserver:address@hidden:/cvs/somedir".  When I do a module checkout, it
always says "cvs [checkout aborted]: cannot start server via rsh: No such
file or directory".

What did I do wrong?  Is the path I put for the module is incorrect or the
ssh thing is not working at all -- I can login to that remote machine to do
a command line cvs checkout.  There is a /cvs/somedir/somefile on that
remote machine and that's what I put for WinCvs as the module name and path.

If you have any suggestions, I would very much appreciate it!

Thanks in advance!
N.







_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs