From d232831135f14e95ef4641fa7e5d62aea0e5b995 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Mon, 31 Jan 2005 08:12:30 +0000 Subject: [PATCH] stop a sigpipe. apparently when we get an eof, at least sometimes it *does* mean you'd better not try writing. svn:r3481 --- src/or/connection_edge.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/or/connection_edge.c b/src/or/connection_edge.c index 16ef484f87..edc8379d15 100644 --- a/src/or/connection_edge.c +++ b/src/or/connection_edge.c @@ -45,8 +45,8 @@ int connection_edge_reached_eof(connection_t *conn) { * get the 'end' right around when the client hangs up on us. */ connection_edge_end(conn, END_STREAM_REASON_DONE, conn->cpath_layer); connection_mark_for_close(conn); - conn->hold_open_until_flushed = 1; /* just because we shouldn't read - doesn't mean we shouldn't write */ +// conn->hold_open_until_flushed = 1; /* just because we shouldn't read +// doesn't mean we shouldn't write */ } return 0; #endif