From: Jakob Østergaard <jakob@unthought.net>
To: Kevin Krieser <kkrieser@delphi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: out of swap
Date: Tue, 28 Nov 2000 16:47:21 +0100 [thread overview]
Message-ID: <20001128164721.I21902@unthought.net> (raw)
In-Reply-To: <3A22EC94.2A434703@mindspring.com> <000b01c058ec$6791abe0$0701a8c0@thinkpad>
In-Reply-To: <000b01c058ec$6791abe0$0701a8c0@thinkpad>; from kkrieser@delphi.com on Mon, Nov 27, 2000 at 09:36:33PM -0600
On Mon, Nov 27, 2000 at 09:36:33PM -0600, Kevin Krieser wrote:
>
> > What would I like it to do? Warn me maybe before my swap goes to
> > zero. Kill the
> > program that is doing this possibly. Allow me to set a per
> > process memory / swap
> > limit so that no one process can suck up my system resources.
> >
>
> There are several programs available with the typical Linux installation
> that allows you to monitor swap space. For example, xosview.
Yep
>
> There are also settings you can make in Netscape that supposedly limit disk
> space usage and memory usage.
But this doesn't help this particular problem, I think. The problem is probably
not the in-memory cache, but the resource consumption caused by netscape
loading the pictures.
You can use ulimit (or pam) to set memory consumption limits for each process,
and that would usually do the trick (see /etc/pam.d/ and
/etc/security/limits.conf at least on RedHat).
Unfortunately, Netscape sends the images to the X server, so usually you will
see that Netscape's memory consumption stays fairly constant, while your X
server will start consuming lots of memory. If you set the resource limits,
your X server will be the obvious choice for the OOM killer (I guess -
comments, Riel or Andrea ?). I don't know of any good solution to this problem
other than just having enough swap space - after all, seriously, with today's
disks, who can't spare an extra few hundred megs (which would usually be more
than enough).
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-28 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 2:05 out of swap Joe
2000-11-28 2:49 ` David Schwartz
2000-11-27 23:21 ` Joe
2000-11-28 3:36 ` Kevin Krieser
2000-11-28 15:47 ` Jakob Østergaard [this message]
2000-11-28 21:08 ` Ben Ford
2000-11-28 21:16 ` Jakob Østergaard
-- strict thread matches above, loose matches on Subject: below --
2000-11-28 2:05 Joe
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=20001128164721.I21902@unthought.net \
--to=jakob@unthought.net \
--cc=kkrieser@delphi.com \
--cc=linux-kernel@vger.kernel.org \
/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