max-connections in incoming.conf
Russ Allbery
rra at stanford.edu
Mon Sep 13 08:44:17 UTC 1999
Katsuhiro Kondou <kondou at nec.co.jp> writes:
> I'm thinking of a new key in incoming.conf; 'nohold' which enables not
> to hold remote connection for PAUSE_BEFORE_DROP(5)*60 seconds. I think
> this is useful if the remote tries to connect excessively for that
> period.
Wouldn't it be better to teach INN to reject connections, with an error,
from a host that has exceeded its max-connections? No new keys needed,
and I think that addresses the case where this change would really be
useful.
> And I found max-connections is effective for each IP address not for
> each label, while I'm trying to implement above. I think this is
> misused, since max-connections can be set to each label, not to each
> hostname which may be a list of remotehosts or may have several IP
> addresses. I'll try to fix it for both STABLE and CURRENT. Any
> comment?
Sounds like a good thing to fix.
--
Russ Allbery (rra at stanford.edu) <URL:http://www.eyrie.org/~eagle/>
More information about the inn-workers
mailing list