From b2b99a70c005ae4158786d0c30b35dc6db45e9b6 Mon Sep 17 00:00:00 2001 From: Sebastian Hahn Date: Sun, 31 Jan 2010 21:54:04 +0100 Subject: Don't spam controllers with TOO_MANY_CONNECTIONS events We implemented ratelimiting for warnings going into the logfile, but didn't rate-limit controller events. Now both log warnings and controller events are rate-limited. --- src/or/connection.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/or/connection.c') diff --git a/src/or/connection.c b/src/or/connection.c index eeb25c182..cf1334574 100644 --- a/src/or/connection.c +++ b/src/or/connection.c @@ -822,9 +822,9 @@ warn_too_many_conns(void) log_warn(LD_NET,"Failing because we have %d connections already. Please " "raise your ulimit -n.", n_conns); last_warned = now; + control_event_general_status(LOG_WARN, "TOO_MANY_CONNECTIONS CURRENT=%d", + n_conns); } - control_event_general_status(LOG_WARN, "TOO_MANY_CONNECTIONS CURRENT=%d", - n_conns); } /** Bind a new non-blocking socket listening to the socket described -- cgit v1.2.3