9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Matthias Teege <matthias-9fans@mteege.de>
To: 9fans@cse.psu.edu
Subject: [9fans] cpu server and swap
Date: Fri, 19 Dec 2003 11:38:26 +0100	[thread overview]
Message-ID: <868yl9gkhz.fsf@gic.mteege.de> (raw)

Moin,

Today I found my (diskless) cpu/auth server with the message

fs killed because no swap configured no physical memory

Ok, I understand but what eats the memory? The machine has 256MB
RAM and reports at startup 2387 free pages, 9548kbytes, 167948k
swap. I run a vmware cpu server with only 64MB RAM without any
problems and stats shows only 10% memory usage. As I understand
cpurc correct, cpu servers don't use swap.

What do I missing?
Matthias

--
Matthias Teege -- http://www.mteege.de
make world not war


             reply	other threads:[~2003-12-19 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 10:38 Matthias Teege [this message]
2003-12-19 11:27 ` Geoff Collyer
2003-12-19 15:19   ` Matthias Teege
2003-12-19 22:59     ` Geoff Collyer
2003-12-20  0:32       ` ron minnich
2003-12-19 14:20 ` mirtchov

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=868yl9gkhz.fsf@gic.mteege.de \
    --to=matthias-9fans@mteege.de \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).