Commit 7201d2e3 authored by Niels Möller's avatar Niels Möller
Browse files

Comment change.

Rev: src/Makefile.am:1.28.2.34
Rev: src/lshd-connection.c:1.1.2.18
parent d7253830
......@@ -40,11 +40,13 @@ bootstrap: $(generated_sources) $(dist_classes)
# Old files:
#
# client_keyexchange.c client_userauth.c connection_commands.c
# debug.c gateway_commands.c
#
# read_packet.c write_packet.c
# client_x11.c server_x11.c client_pty.c tcpforward_commands.c
# Obsoleted files: read_data.c read_file.c read_line.c abstract_io.c write_buffer.c channel_commands.c string_buffer.c handshake.c lshd_keyexchange.c
# Obsoleted files: read_data.c read_file.c read_line.c abstract_io.c
# write_buffer.c channel_commands.c string_buffer.c handshake.c
# lshd_keyexchange.c debug.c gateway_commands.c
liblsh_a_SOURCES = algorithms.c alist.c arglist.c atoms.c \
......
......@@ -104,7 +104,11 @@ blocking_writev(int fd, struct iovec *iv, size_t n)
return 1;
}
/* NOTE: Uses blocking mode. Doesn't set any sequence number. */
/* NOTE: Uses blocking mode. Doesn't set any sequence number. The
reason we may get away with blocking mode, is that it's primarily
the client's responsibility to consume data and avoid dead locks.
But that may not be enough if we're forwarding channels with
reversed client/server responsibilities. */
static void
write_packet(struct connection *self, struct lsh_string *packet)
{
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment