max-connections in incoming.conf

The Hermit Hacker scrappy at
Mon Sep 13 13:49:53 UTC 1999

On Mon, 13 Sep 1999, Katsuhiro Kondou wrote:

> In article <ylogf76w0u.fsf at>,
> 	Russ Allbery <rra at> wrote;
> } 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.
> I think so, but that part of the code was written by Marc,
> and he said, if I remember correctly, his peer tries to
> connect quickly after the disconnect and he wanted to hold
> a while not to reconnect again.

Exactly...but, if you are going to dive in and make changes, why not make
a 'hold-time' variable instead of 'nohold'?  that way you could set it for
0 for nohold, or 600 for 10 minutes, or...whatever you want, instead of
hte fixed time I originally created it as?

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ 
primary: scrappy at           secondary: scrappy@{freebsd|postgresql}.org 

More information about the inn-workers mailing list