search for: fdout_bytes

...N)) { +294 /* do nothing */ +295 } else if (len <= 0) { +296 fdout_eof = 1; +297 } else { +298 buffer_append(&stdout_buffer, buf, len); +299 fdout_bytes += len; +300 } +301 } +302 /* Read and buffer any available stderr data from the program. */ +303 if (!fderr_eof && FD_ISSET(fderr, readset)) { +304 len = read(fderr, buf, sizeof(buf)); +305 if...

...(buffer_len(&stderr_buffer) == 0)) { if (!channel_still_open()) break; as well as other useful logging information, like: debug("End of interactive session; stdin %ld, stdout (read %ld, sent %ld), stderr %ld bytes.", stdin_bytes, fdout_bytes, stdout_bytes, stderr_bytes); which aren't in the v2 server_loop2. I'd suggest a patch here, but I don't know enough about the code nor protocols to know how much these v1 conventions can be applied to v2. It sure would be nice to have a v2 connection log the same information a v1...

...N)) { +308 /* do nothing */ +309 } else if (len <= 0) { +310 fdout_eof = 1; +311 } else { +312 buffer_append(&stdout_buffer, buf, len); +313 fdout_bytes += len; +314 } Line # 309 needs to be changed to ... +309 } else if (len < 0) { Making the above change in the 2.3.0p1 and the 2.5.1p1 source distributions solves the problem, however, I don't know if there might be any other ill effect, or if th...

http://bugzilla.mindrot.org/show_bug.cgi?id=124 ------- Additional Comments From markus at openbsd.org 2002-02-23 06:10 ------- what does "streaming" mean? what does "output reports" mean? do you have more detailed reports? do you have debugging output? what clients are involved? what servers? does the same happen with openssh 3.0.2? does the same happen with a recent