On 2016-05-12 19:47:17 [-0300], Felipe Sateler wrote:
> > This functionality will come with systemd 230:
> > https://github.com/systemd/systemd/pull/3148 , so nothing out of the
> > box yet.
> >
> > A more involved solution (but working right now) would be to have
> >
On 12 May 2016 at 19:43, Felipe Sateler wrote:
> On 12 May 2016 at 18:55, Sebastian Andrzej Siewior
> wrote:
>> On 2016-05-11 12:12:42 [-0400], Joey Hess wrote:
>>> Looks like it was being killed each time by the OOM killer. Which makes
>>> sense;
On 12 May 2016 at 18:55, Sebastian Andrzej Siewior
wrote:
> On 2016-05-11 12:12:42 [-0400], Joey Hess wrote:
>> Looks like it was being killed each time by the OOM killer. Which makes
>> sense; clamav uses 18% of the system's 2 gb of ram and so will be the
>> top target.
On 2016-05-11 12:12:42 [-0400], Joey Hess wrote:
> Looks like it was being killed each time by the OOM killer. Which makes
> sense; clamav uses 18% of the system's 2 gb of ram and so will be the
> top target.
>
> I think there should be something to prevent this runaway scenario.
> Maybe a delay,
Package: clamav-daemon
Version: 0.99.1+dfsg-1+b2
Severity: normal
clamav-daemon got into a loop on my server where it was being killed and
restarting multiple times per second. This spiked load to 100.
Basically a weak fork bomb.
I tried systemctl stop clamav but it just started right up again.
5 matches
Mail list logo