Thus said David Mason on Tue, 09 Feb 2016 14:25:41 -0500: > This time the (new) student has not committed successfully, and on any > attempt to write gets "Unable to write to standard output: The pipe is > being closed." This is using SSH/PLINK on Windows.
Is this error a client error or something seen in the server? It doesn't appear to be a Fossil error: $ grep 'Unable.to.write.to.standard.output' *.c $ echo $? 1 > I ran "fossil sync --sshtrace" and saw exactly the headers I'd expect > (200, etc). Can you run with both --sshtrace and --httptrace (maybe even throw in --verbose) to see what is actually being sent? Any chance you can post the output and results somewhere? >From the error, I would conclude that Fossil (client) tried to write data into the SSH process, but that the process had already closed its pipe. Why would it do that unless the Fossil (server) on the remote end thought that the conversation was over (or it crashed)? Andy -- TAI64 timestamp: 4000000056ba584e _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
