I am trying to bring about a fix for the bad interaction between
CVS and SSH that causes data to be lost?
See <http://lists.gnu.org/archive/html/bug-cvs/2002-07/msg00423.html> for
a good explanation.
After studying that message, I think I understand the problem. It
occurs when the stdout of cvs equals the stderr of ssh. When ssh sets
O_NONBLOCK on that descriptor, cvs gets confused.
This problem has gone unfixed because neither CVS nor SSH is doing
something clearly wrong. Nonetheless, the combination of the two
are doing something wrong, so we need to fix it somewhere.
Couldn't this be fixed easily by changing cvs to handle EAGAIN
in a simple way when outputting to stdout? If it just sleeps for a second
and tries again, that ought to fix the problem.
Is there someone who can fix this? Please respond, if you are working
on CVS.
_______________________________________________
Bug-cvs mailing list
Bug-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cvs
