On Tue, Feb 26, 2002 at 02:12:06AM -0800, Karsten M. Self wrote:
[...]
| I'd had exim running from inetd rather that as a daemon, which might
| also explain the many forkings.
[...]
Yeah, that would have an effect on it. If exim runs as a daemon, then
it can monitor and control the various forks of it. If it is run from
(x)inetd, then the super-daemon can unwittingly create many parallel
"main" exim processes and exim can't control it's total system load.
There's also the _potential_ for creating an open relay if (x)inetd
isn't configured exactly right. See the exim-users list archives for
a rather in-depth discussion of the issue and possible fixes. The
best thing, IMO, is to just run exim as a daemon. If you're on a
dial-up box, then there is no reason to daemonize it in any form
(either with or without (x)inetd).
-D
--
Many a man claims to have unfailing love,
but a faithful man who can find?
Proverbs 20:6
