> > Good, so the OOM killer works.
>
> But it doesn't work for this kind of application misbehaviours (or
> user attacks):
>
> main() { while(1) if (fork()) malloc(1); }
This seems to be a fork() bomb, not a VM issue. The system is overwhelmed by
the the forks, not by the space consumed by the al
On Tue, 14 Nov 2000, Erik Mouw wrote:
> On Mon, Nov 13, 2000 at 10:50:05PM +0100, Szabolcs Szakacsits wrote:
> > But it doesn't work for this kind of application misbehaviours (or
> > user attacks):
> > main() { while(1) if (fork()) malloc(1); }
> Proper process limits stop the fork bomb.
You co
Michael Peddemors wrote:
>
> > up to the sysadmin to enforce the policy. For the home user it means
> > that the distribution providers have to set decent limits,
>
> What is decent today may not be with tommorows' newest softwares
>
Which is why you upgrade your distribution now and then.
> up to the sysadmin to enforce the policy. For the home user it means
> that the distribution providers have to set decent limits,
What is decent today may not be with tommorows' newest softwares
> for enterprises it means that they have to hire a sysadmin.
That is one of the reasons that
On Mon, Nov 13, 2000 at 10:50:05PM +0100, Szabolcs Szakacsits wrote:
> On Mon, Nov 13, 2000 Erik Mouw wrote:
> > Good, so the OOM killer works.
>
> But it doesn't work for this kind of application misbehaviours (or
> user attacks):
>
> main() { while(1) if (fork()) malloc(1); }
Proper process l
On Mon, Nov 13, 2000 Erik Mouw wrote:
> On Mon, Nov 13, 2000 at 05:29:48PM +0530, [EMAIL PROTECTED] wrote:
> > System becomes useless till all of the instance of this programming are
> > killed by vmm.
> Good, so the OOM killer works.
But it doesn't work for this kind of application misbehaviou
6 matches
Mail list logo
