Mark Tinguely wrote:
Is it possible that there's a message in your queue that's *being
processed*, so it may have arrived earlier than near that time and
causes the spike?
Bart is correct that the SA processing occurs before sendmail log entry.
Lately, I have had problems with the latest s
> Is it possible that there's a message in your queue that's *being
> processed*, so it may have arrived earlier than near that time and
> causes the spike?
Bart is correct that the SA processing occurs before sendmail log entry.
Lately, I have had problems with the latest spamass-milter. O
Zbigniew Szalbot wrote:
Hello,
2008/2/27, Mark Tinguely <[EMAIL PROTECTED]>:
> >From the MRTG data I can see that suddenly on a currently not very
> busy machine the load averege went over 15 or more. This happened
> around 10 in the morning. Not many entries in httpd access log, smtp
>
Hello,
2008/2/27, Mark Tinguely <[EMAIL PROTECTED]>:
>
> > >From the MRTG data I can see that suddenly on a currently not very
> > busy machine the load averege went over 15 or more. This happened
> > around 10 in the morning. Not many entries in httpd access log, smtp
> > server was not t
> >From the MRTG data I can see that suddenly on a currently not very
> busy machine the load averege went over 15 or more. This happened
> around 10 in the morning. Not many entries in httpd access log, smtp
> server was not too much loaded (at that time it generally produces a
> load averag
Hello,
2008/2/27, Kris Kennaway <[EMAIL PROTECTED]>:
> Zbigniew Szalbot wrote:
> > Hello,
> >
> >>From the MRTG data I can see that suddenly on a currently not very
> > busy machine the load averege went over 15 or more. This happened
> > around 10 in the morning. Not many entries in httpd ac
Zbigniew Szalbot wrote:
Hello,
From the MRTG data I can see that suddenly on a currently not very
busy machine the load averege went over 15 or more. This happened
around 10 in the morning. Not many entries in httpd access log, smtp
server was not too much loaded (at that time it generally pro
