| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090118131303.GA19292@ioremap.net> Date: Sun, 18 Jan 2009 16:13:03 +0300 From: Evgeniy Polyakov <zbr@...emap.net> To: Bodo Eggert <7eggert@....de> Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [why oom_adj does not work] Re: Linux killed Kenny, bastard! On Sun, Jan 18, 2009 at 01:37:09PM +0100, Bodo Eggert (7eggert@....de) wrote: > How many different CGI handlers are you going to have? CGIs are usually limited, application server is not. > And how does kill-kenny scale with the number of users on the system? > I want my browser not to be killed, while the other user wants his > gimp not to be killed. As you can see, it does not even scale for > the most simple multi-user system. It is not about who should not be killed, but who should _be_ in the first raw. > > No, admin will limit/forbid the connection from the DoSing clients, > > server must always live to handle proper users. > > If there is no memory, the admin can't even log in. Admin can observe the situation via kvm or sometimes netconsole and tune the system for the next run. -- Evgeniy Polyakov -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists