I'm reviving a question about a problem from a year ago that was never satisfactorily resolved (the student gave up and never replied to my request for --sshtrace).
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. I ran "fossil sync --sshtrace" and saw exactly the headers I'd expect (200, etc). The student.fossil file on the remote server appears to have been written to by the clone command, but not by the commit or sync. I expect this is the case for MANY of the students using Windows. Because of other issues (which I'll address separately) the remote directory has 777 permissions and the remote fossil has 666. The other issues *might* be the same problem but we get different responses from Windows and Mac. ../Dave On 26 March 2015 at 15:42, David Mason <dma...@ryerson.ca> wrote: > Me again... :-) > > I have a student running Windows using the current fossil as of January. > > 1) PLINK.EXE works so there's no ssh problem. > 2) She has successfully committed before. > 3) She tried to commit and got a "Would fork" so > 4) She did an update > 5) then commit she got "Unable to write to standard output: The pipe is > being closed." on the autosync part. > 6) Subsequent sync does same think - after her command prompt has been > printed. > > I thought I'd seen this on the list, but google only gives one hit (in > Japanese) on part of the search string. > > Any ideas? > > Thanks ../Dave >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
