Displaying 2 results from an estimated 2 matches for "stdout_bytes".
Did you mean:
fdout_bytes
2001 Oct 17
3
Bug when flushing data in openssh 2.9
...(buffer_len(&stdout_buffer) > 0) {
len = write(fileno(stdout), buffer_ptr(&stdout_buffer),
buffer_len(&stdout_buffer));
! if (len <= 0) {
! error("Write failed flushing stdout buffer.");
! break;
}
buffer_consume(&stdout_buffer, len);
stdout_bytes += len;
--- 937,953 ----
}
/* Output any buffered data for stdout. */
while (buffer_len(&stdout_buffer) > 0) {
+ errno=0; /* Linux doesn't reset this */
len = write(fileno(stdout), buffer_ptr(&stdout_buffer),
buffer_len(&stdout_buffer));
! if (len...
2000 Aug 08
0
v2 connection logging vs v1
...r_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
connection doe...