Thanks, yes, but,
I have set up a similar system many times previously and always used SuSE
Linux with daemontools and ucspi-tcp, no problems at all.
However this particular system is RedHat 8, and I was having big problems with
daemontools processes just dying (big list of <defunct> processes). This was
reported by others here and there but I never saw (or found) a decent
explanation - I rather came to the conclusion that daemontools was broken in
some way. Hence backing off to the old fashioned solution.
It is worth noting that this is a *very* low-use mail server, its just used
for a small department/project and only has about 6 users, which is why I
wasn't too worried in the first place. 50 incoming connections strikes me as
extremely unlikely, unless of course something else nasty has happened.
On Friday 04 July 2003 09:39, Kiril Todorov wrote:
> On Fri, Jul 04, 2003 at 08:52:56AM +0100, Howard Miller wrote:
> > > what's your pop3d run script?
> > I am using xinet, so...
> And that's exactly your problem :>
> cut from xinetd.conf (5)
> Limits the rate of incoming connections. Takes two arguments.
> The first argument is the number of connections per second to handle.
> If the rate of incoming connections is higher than this, the service
> will be temporarily disabled. The second argument is the number of
> seconds to wait before re-enabling the service after it has been disabled.
> The default for this setting is 50 incoming connections and the
> interval is 10 seconds.
> As written on qmail.org, qmail is recommended to be run with tcpserver and
> daemontools, and inetd, xinetd are not supported anymore.
> If you need a hand how to set up daemontools and ucspi-tcp heres is a good
> howto on that: http://flounder.net/qmail/qmail-howto.html
> G'luck :>