On 08/06/17 19:59, Curtis NPC wrote:
> Ok, I was premature in that. I was worried that several amavis processes
> were going to start up again.
> Eventually that process that I described disappeared. But I wonder why
> it was taking so long (5-10 minutes) and so much CPU?
It's hard to know
what is the operating system?
On Tue, Jun 13, 2017 at 2:13 PM, Tilman Schmidt
wrote:
> As a guess, it was probably scanning a big attachment.
>
> ObAdvice: *don't* use kill -9.
>
> HTH
> T.
>
> On 08.06.2017 20:59, Curtis NPC wrote:
> > Ok, I was premature in that. I was
As a guess, it was probably scanning a big attachment.
ObAdvice: *don't* use kill -9.
HTH
T.
On 08.06.2017 20:59, Curtis NPC wrote:
> Ok, I was premature in that. I was worried that several amavis processes
> were going to start up again.
> Eventually that process that I described disappeared.
Ok, I was premature in that. I was worried that several amavis
processes were going to start up again.
Eventually that process that I described disappeared. But I wonder why
it was taking so long (5-10 minutes) and so much CPU?
On 2017-06-08 18:38:30 +, Curtis NPC said:
Now I've noticed
Now I've noticed that amavis is taking up 100% of the CPU. In fact just
a few minutes ago I had several amavis processes running at the same
time, all sucking up resources.
I had to stop all mail related services. Kill -9 on all amavis
processes and then restart them all. Things were calm for a