BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] memory management
- Subject: [Discuss] memory management
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Mon, 22 Jun 2015 19:34:32 -0400
- In-reply-to: <55888EC5.6050004@mattgillen.net>
- References: <558420D5.6090803@mattgillen.net> <55858DB0.4080709@mattgillen.net> <55885E49.8040902@mattgillen.net> <5588644A.8010602@gmail.com> <55888EC5.6050004@mattgillen.net>
On 6/22/2015 6:40 PM, Matthew Gillen wrote: > That doesn't (necessarily) address the issue I was raising about an out > of control app wreaking havoc on the rest of the system. Just a > different flavor of havoc. Yes, it does. The kernel isn't there to baby sit. It's there to allocate resources when processes request them. It is up to you, the user or the administrator, to manage those processes. It isn't the kernel's responsibility to do this for you. Hint: man prlimit -- Rich P.
- Follow-Ups:
- [Discuss] memory management
- From: abreauj at gmail.com (John Abreau)
- [Discuss] memory management
- References:
- [Discuss] memory management
- From: me at mattgillen.net (Matthew Gillen)
- [Discuss] memory management
- From: me at mattgillen.net (Matthew Gillen)
- [Discuss] memory management
- From: me at mattgillen.net (Matthew Gillen)
- [Discuss] memory management
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] memory management
- From: me at mattgillen.net (Matthew Gillen)
- [Discuss] memory management
- Prev by Date: [Discuss] A laptop for Linux
- Next by Date: [Discuss] A laptop for Linux
- Previous by thread: [Discuss] memory management
- Next by thread: [Discuss] memory management
- Index(es):