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.
This commit is contained in:
Sebastian Hahn
2010-01-31 21:54:04 +01:00
parent 080e8f50f8
commit b2b99a70c0
2 changed files with 5 additions and 2 deletions
+2 -2
View File
@@ -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