From: john slee <indigoid@higherplane.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Memory Leaking. Help!
Date: Mon, 15 Apr 2002 16:10:31 +1000 [thread overview]
Message-ID: <20020415061031.GN11940@higherplane.net> (raw)
In-Reply-To: <E16wu4J-00057Y-00@the-village.bc.nu> <Pine.LNX.4.33.0204151017480.20961-100000@dipole.es.usyd.edu.au> <20020415011834.B16804@pizzashack.org>
On Mon, Apr 15, 2002 at 01:18:34AM -0400, xystrus wrote:
> On Mon, Apr 15, 2002 at 10:28:00AM +1000, ivan wrote:
> > That was 4 GB not 2.
> >
> > No, I do not. That is why I asked is there a way to find out what is
> > eating ram. I am not sure if this a leakage. I am only a paranoid
> > sysadmin.
> >
>
> I think you said this was a server, didn't you?
>
> You neglected to mention that you're running X and Nautilus on this
> server. You probably don't need this stuff running on a server, and
> it is chewing up a good amount of RAM. If you don't absolutely need
> X, try bringing the system up in run level 3 and see if your problem
> disappears...
it could be a server for x11-based thin clients
--
R N G G "Well, there it goes again... And we just sit
I G G G here without opposable thumbs." -- gary larson
next prev parent reply other threads:[~2002-04-15 6:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-14 12:23 Memory Leaking. Help! ivan
2002-04-14 13:15 ` Itai Nahshon
2002-04-14 14:05 ` Alan Cox
2002-04-14 22:51 ` ivan
2002-04-15 0:10 ` Alan Cox
2002-04-15 0:28 ` ivan
2002-04-15 5:18 ` xystrus
2002-04-15 6:10 ` john slee [this message]
2002-04-15 9:09 ` Alan Cox
2002-04-15 10:00 ` David Schwartz
2002-04-15 12:25 ` Eugenio Mastroviti
2002-04-15 15:59 ` Kervin Pierre
2002-04-16 0:36 ` David Schwartz
2002-04-15 11:30 ` Roy Sigurd Karlsbakk
2002-04-15 0:03 ` Tomasz Rola
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=20020415061031.GN11940@higherplane.net \
--to=indigoid@higherplane.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.