CVS Proxy leaves unclosed processes plink.exe

( CVSSCC )

Type: Public Status:Closed Created: 11 Mar 04 03:00 Updated: 11 Mar 04 03:00

--> Alexander Muratov (user) at 11 Mar 04 03:00 writes

Thank you for advise. I will try this solution definitely.
Best regards,
Alex.

--> Igor Pushkov (admin) at 11 Mar 04 03:00 writes

) So you offer me to move from UNIX CVS to CVS NT? ;)
No, I just offer you to use CVS NT as _client_ for yout LINUX server.
This makes a sense :)
E.g. we have a LINUX CVS on our local server, but in the same time we
use CVS NT cvs.exe (its client part) to access to LINUX server.
And you can use advantages of CVS NT _client_ part, which support
:ssh: protocol.
CVS NT as _client_ compatible with UNIX server. And more, you
already use it, since only cvs95.exe is native linux port, but cvs.exe
that shipped with WinCVS or our plugin is CVS NT cvs.exe (see cvs
-version).
:ssh: protocol on CVS NT client is the same for server as :ext:
protocol. :ssh: protocol appears in CVS NT _client_ from version
2.0.xx. That's why I suggest to use cvs.exe shipped with our plugin
(its version 2.0.26). Which version of CVS NT _client_ have you WinCVS
I not know.

--> Alexander Muratov (user) at 11 Mar 04 03:00 writes

Hi!
So you offer me to move from UNIX CVS to CVS NT? ;)
Unfortunately we are not ready to do it.
Best regards,
Alex.

--> Igor Pushkov (admin) at 11 Mar 04 03:00 writes

We checked this, however cannot repeat this behavior. But while
testing I found something interesting for you.
As I told, CVS NT have built-in support for SSH connections, I not
tried it before, but now does.
What I find:
1. It _much more_ faster than cvs.exe+plink.exe, may be up to 2-3
times.
2. It is _not need_ to setup password less connection.
3. SSH support is located in dll, so you will not have problems with
'plink.exe' processes.
Now, the descriptions how to establish it:
1. Protocol in CVSROOT is :ssh: not :ext:
:ssh:Serg:geiney@ksvhost.dyndns.org:/usr/pushok/cvs
instead of
:ext:Serg:geiney@ksvhost.dyndns.org:/usr/pushok/cvs
2. Having all advantages of ssh (:ext) protocol works like :pserver:,
i.e. you need to "cvs login" first. Unfortunately just for now you
cannot do this from plug-in (we support login command but it is not
work with this protocol). So you need go to the plugin installiation
folder and type something like:
cvs -d :ssh:Serg@ksvhost.dyndns.org:/usr/pushok/cvs login
3. After that you can use IDE and plug-in as usual. IMPORTANT, you
should configure plug-in to use default cvs.exe (shipped with program)
Look at original description at: http://www.cvsnt.org/wiki/CvsChapter28
Let me know if this useful.

--> Alexander Muratov (user) at 11 Mar 04 03:00 writes

There is set of plink.exe only. cvs.exe is closed after operation. But I
don't understand what is the difference when I use WinCVS or CVS Proxy. I
didn't find exact sequence when plink.exe is left. Sometimes CVS operation
leaves it but sometimes not.
I tried to cvs.exe and cvs95.exe from WinCVS 1.3, there is no difference.
The latest CVS Proxy update didn't solve this issue.

--> Igor Pushkov (admin) at 11 Mar 04 03:00 writes

You see only leaked "plink.exe" processes or also "cvs.exe"? Anyway we
will test this on our side, and I will inform you on results.

--> Alexander Muratov (user) at 11 Mar 04 03:00 writes

I find out that during work with CVS Proxy from MS Visual C++ 6.0/eMbedded
VC ++ via plink.exe CVS Proxy leaves several plink.exe processes unclosed.
Number of these processes is growing and finally it causes overflow of open
file table on the UNIX server.
It doesn't happen when we use WinCVS
Proxy was configured to use cvs.exe from WinCVS 1.3 folder.

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

CVS Proxy leaves unclosed processes plink.exe