Re: cvs history sends incorrect data

[cvs]

But why this problem only occurs in the history command? Everything else 
works well. Even with CVSNT the history command works well.

--
Best regards,
Thomas Singer
_____________
smartcvs.com


Larry Jones wrote:

> Thomas Singer writes:
>
> > But much more weird it is, that this problem only seems to occur, when I 
> > use SSH to communicate with the server. With local access this problem 
> > does not happen. But it could not be a problem with the SSH client or 
> > server, because everything else works fine and the 'ok' reponse also is 
> > sent correctly.
>
>
> Ah, that rings a bell.  There's a problem where SSH puts some of its
> file descriptors into non-blocking mode, which CVS doesn't expect.  If
> CVS then writes data faster than the receiver reads it, stuff gets lost.
> See this thread for all the gory details and possible work-arounds:
>
>         <http://lists.gnu.org/archive/html/bug-cvs/2002-07/msg00084.html>
>
> -Larry Jones
>
> What a waste to be going to school on a morning like this. -- Calvin
>
>
> _______________________________________________
> Bug-cvs mailing list
> Bug-cvs@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-cvs