petepo wrote:
> How many process of Exim should be running?
>
> As attached below is the process running in my system -
> Can any kind soul advise? Thanks.
>
> exim 21363 1 0 09:34 ? 00:00:00 /usr/sbin/sendmail -bd -q1h
> exim 25848 1 0 10:42 ? 00:00:00 /usr/sbin/sendmail -bd -q1h
> exim 25888 25848 0 10:42 ? 00:00:00 /usr/sbin/sendmail -bd -q1h
> exim 25891 25848 0 10:42 ? 00:00:00 /usr/sbin/sendmail -bd -q1h
> exim 25894 25848 0 10:42 ? 00:00:00 /usr/sbin/sendmail -bd -q1h
> root 26019 25713 0 10:42 pts/5 00:00:00 grep sendmail
A minimum of one - what amounts to the listener/dispatcher, will run even if the
network cable is unplugged.
Then one more per connection, plus one for each message being processed or queue
runner. 'exiwhat' will let you know what each of them is doing.
So two is about the minimum if there is even very sparse activity.
How the rest computes depends on whether you are handling delivery at once, or
in queue-only mode, how often you call a 'run regardless' queue runner, etc.
- and, of course, how much traffic you are handling at a given point in time.
We run with connection limits and such, but typically see anywhere from 4 to 4
dozen running at any given time, average about 6 to 10. Highest I have seen,
IIRC was just under 150 when testing rather longish cumulative penalty delays
AND being flooded from a zombie farm.
If in doubt, 'nice' exim down and look to connection and message limiting, plus
- only if it suits you - modest delays for rude behaviour.
The process count may go up, but the resources consumed can actually go down as
some of these will be sitting and waiting. Zombies tend to be very impatient,
and often abandon the connection rather than wait even 30 seconds, let alone a
minute or two.
YMMV
Bill
