[cvsnt] Ssh protocol && socket error

[Paul Blair]

OK, I found out a way around the problem, for my purposes. My code had
iterated over a list of modules, first doing an rtag and then an export
for each module. CVS would hang once or twice during the process, usually
(but not always) after it had just finished checking out a big module.

What I'm doing instead now is passing a list of projects to a single rtag
command line, and then the same list of projects to export. This hasn't
hung on me yet.

Otherwise, I love the ssh protocol!

Paul Blair wrote:

> OK, I'm up to CVSNT 2.0.11 and am still getting the same socket 
> error Keith reported back in January. I've searched the CVSNT 
> archive for any other discussion of this issue and haven't 
> found anything--any updates?

> The symptoms I'm seeing is that when checking out a number of
> different projects using the :extssh: protocol, the CVS client 
> sometimes hangs. Setting compression to 0 means that it hangs 
> more often, setting compression to 9 means that it hangs less 
> often--but I rarely get through an entire checkout of 17 
> assorted projects without at least one, and usually two, hangs.
> Most of the time CVS hangs after finishing checking out the
> largest projects, but not always.

> Thanks,

> Paul

> On Fri, 31 Jan 2003 14:55:07 GMT Tony Hoyle <tmh at nodomain.org> wrote:

> >On Fri, 31 Jan 2003 09:20:25 -0500, "Keith D. Zimmerman"
> ><kzimmerman at eshcom.com> wrote:
> >
> >>I am trying to use the new :ssh: protocol in cvsnt.  Whenever I do cvs
> >>update on a small repository, it works ok.  If I do cvs update on a
> >>larger one, it'll fail.  If I use compression, it'll work in that one,
> >>but then I move on to an even larger one, and no matter what I do with
> >>compression, it fails.  It seems like the protocol fails when dealing
> >>with a large list of updates...
> >>
> >>The error message I am getting is:
> >>       cvs [update aborted]: writing to server socket: error -1
> >>
> >>Any ideas?  Is there a better way to use ssh with cvsnt?  Or a better
> >>way to give external, encrypted access?
> >
> >Make sure you're using the latest version, as ssh is constantly
> >improving (the repository size issue sounds like something I fixed a
> >couple of versions ago).   At he moment using something like plink.exe
> >with :ext: is more stable if you want fewer hassles (more people have
> >experience with it so it's probably easier to solve problems).
> >
> >Tony