[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WinCVS Over SSH Hangs

From: Rene Berber
Subject: Re: WinCVS Over SSH Hangs
Date: 24 May 2002 15:25:39 -0700

Fred Quimby <address@hidden> wrote in message news:<address@hidden>...

> This is similar to the "CVS over SSH hangs' thread but is not the same 
> problem.
> First the details:
> Solaris 7 server
> Win2k client
> CVS 1.11.1p1 (client/server)
> WinCvs or
> SSH client is any of these
>   1) PuTTY 0.51, 0.52, or 0.52+ (bleeding edge).
>   2) OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
>   3) SSH Secure Shell 3.1.0 Windows Client
> Now the problem: I can open an ssh session using any of the clients 
> directly and authenticate using password or passphrase authentication. 
> Commands like "ssh address@hidden cvs version" work fine.

Warning: read the WinCVS manual, it recommends that you set up your
ssh configuration in such a way that you do not need to enter
passwords or pass-phrases; otherwise, no matter what version you use,
a "command prompt" window will always open (not a nice panel, like it
happens with pserver), most times minimized so you have to search for
it, and in that window you'll have to enter the password.

You don't have to get rid of password and pass-phrase, you only have
to configure ssh and key-handling for the later.

> However, if I set WinCvs up to use ssh authentication, the cvs Console 
> Window fails to terminate. WinCvs reports the command issued, 
> information requested, and "CVS exited normally with code of 0" BUT THE 
> CONSOLE WINDOW IS STILL OPEN and the 'fish' swimming. Killing the 
> concole window lets things continue normally and cause any further 
> problems under W2k but causes an exception error under W98.
> Recent changes: I upgraded to WinCvs 1.3.8 and PuTTY 0.52 when I first 
> noticed the problem. I've sence gone back to 1.3.7 and 0.51 but still 
> have the problem.
> Help?

OK, first: this is normal operation with WinCVS; at least with the
versions you are using.  If you want a little better behaviour (but
not perfect) go back to version 1.3.6 .

Second, you say you prefer 1.3.7, I don't agree ... that version had
so many bugs that I stopped using it after one day.

Last, the description of a persistent command window that needs to be
closed by hand so WinCVS ends the operation sounds like a problem I
been having with WinCVS (1.3.6 and 1.3.8) and JBuilder 6, but it only
happens when I use in the server side CVS 1.11.2, going back to
1.11.1p1 solved those "processes" hanging.   You are using the older
version so I don't really know what to make of this.

Anyway, hope this info helps.
R. Berber
rberber AT mailandnews . com

reply via email to

[Prev in Thread] Current Thread [Next in Thread]