We finally found the problem. It was neither CVS or SSH that
was the issue. The developer had recently had a couple of
anti-virus programs run out of their evaluation periods.
They were preventing the file transfer from occuring. *sigh*
Thanks for the responses anyway, we'll keep them on
[ On Thursday, April 20, 2000 at 15:15:59 (-0700), Cindy Hahn wrote: ]
Subject: cvs over ssh ugliness
From watching the
server, he is authenticating correctly and then the process
running his cvs command just blocks and never executes. On
the client side it just completely hangs. Taking
I have cvs setup on a Linux box. I connect from Windows 2000 and NT4 via
ssh. The first time a run a command everything runs perfectly, but if I try
to run another command in the next five minutes i get the following error:
No Warranty! Read COPYING licence available with src, and redistribute
On Fri, Apr 21, 2000 at 10:17:51AM -0400, Greg A. Woods sent forth:
[ On Thursday, April 20, 2000 at 15:15:59 (-0700), Cindy Hahn wrote: ]
ssh -v host.domain id
If the user can do that then the problem is not likely with SSH but
rather with how CVS invokes SSH, or with the CVS
Hi all,
I'm in charge of the CVS stuff for our Engineering deptartment
and we're seeing something really funky and incredibly frustrating.
One of the developers cannot checkout any projects from the CVS
repository. He's running Win98, WinCVS 1.0.6 (we also tried
WinCVS 1.1b12 to no avail), ssh
