Displaying 1 result from an estimated 1 matches for "stdin_bytes".
2000 Aug 08
0
v2 connection logging vs v1
...p;&
(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 info...