From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrea <andrea256it@yahoo.it>,
linux-kernel@vger.kernel.org
Subject: Re: super root shell/mode/api
Date: Wed, 20 May 2009 07:03:27 +0100 [thread overview]
Message-ID: <20090520060327.GB31552@sucs.org> (raw)
In-Reply-To: <20090520043603.GA9725@1wt.eu>
On Wed, May 20, 2009 at 06:36:04AM +0200, Willy Tarreau wrote:
>
> I don't know if mainline distros do this, but some distros dedicated to
> embedded systems have been using that for ages, almost since Alan published
> his first overcommit patch a long time ago. It's the only way to reach
> very long uptimes on servers, as it also protects you against your own
> mistakes (eg: stupid actions such as "vi access.log" when the file is
> larger than memory).
Shouldn't the vi case be taken care of by good ulimits? Certainly that's
what I've seen openSUSE do by default (although strangely SLES 10
doesn't)...
The last I heard about overcommit was that there were always some
legitimate programs that could run that would be stopped by having it on
(evolution always seemed to be mentioned for some reason). As such it
would be surprising to see any of the desktop distros enabling it by
default.
I've been wondering for a while with my EeePC if strict overcommit is a
no brainer if you are running without swap... In such systems the only
things that can be forced out of RAM are mmap'd files (?) so does
overcommit even happen?
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2009-05-20 6:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 13:06 super root shell/mode/api Andrea
2009-05-17 15:02 ` Andi Kleen
2009-05-18 9:35 ` Alan Cox
2009-05-18 16:12 ` Henrique de Moraes Holschuh
2009-05-20 4:36 ` Willy Tarreau
2009-05-20 6:03 ` Sitsofe Wheeler [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-17 17:13 Andrea
[not found] <cCSbU-L3-17@gated-at.bofh.it>
2009-05-18 22:56 ` Bodo Eggert
2009-05-19 14:36 Andrea
2009-05-19 14:54 ` Alan Cox
2009-05-23 13:23 ` Bodo Eggert
2009-05-23 13:50 ` Joao Correia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090520060327.GB31552@sucs.org \
--to=sitsofe@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea256it@yahoo.it \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox