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:
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
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
On 3/26/15, 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
Thus said David Mason on Thu, 26 Mar 2015 15:42:41 -0400:
6) Subsequent sync does same think - after her command prompt has been
printed.
Does ``fossil sync'' work?
Also, to get more verbose output from Fossil, you can do:
fossil sync --sshtrace
Thanks,
Andy
--
TAI64 timestamp:
Thus said David Mason on Thu, 26 Mar 2015 15:42:41 -0400:
5) then commit she got Unable to write to standard output: The pipe
is being closed. on the autosync part.
It sounds like something with the SSH connection failed but didn't get
output. Does plink have any debug options that can
6 matches
Mail list logo
