From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] install "out of physical memory"
Date: Mon, 18 Sep 2006 07:10:50 +1000 [thread overview]
Message-ID: <775b8d190609171410q4dacb30bm2ed211fcf87c821b@mail.gmail.com> (raw)
In-Reply-To: <ebe9fa06c3f2185523de140087923223@plan9.bell-labs.com>
i've never had problems with swap. my setup at the labs was diskless
"terminal" with lotsa ram and swap on /n/other. it never failed, tho swap
was really only there to cope with extraordinary circumstances.
i have a similar setup in sydney tho "other" is local.
killing a random process is not a solution. it's an egregious hack.
brucee
On 9/18/06, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
> It's not automatic; you need to add something like
>
> swap /dev/sdC0/swap
>
> to cpurc or cpurc.local. Others feel that there are serious bugs in
> the swapping (paging) code but I've had good luck with it.
>
> If you expect to swap regularly, you should keep any local file
> systems on different disks from your swap space, or performance will
> suffer badly when you swap. It's also possible to swap to a file
> server (e.g., `swap /n/other/swap') but you'll want to use switched
> Ethernet if you do that. If it's possible, it's almost certainly a
> better idea to add more RAM to your machine.
>
next prev parent reply other threads:[~2006-09-17 21:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 14:06 chuckf
2006-09-17 18:31 ` erik quanstrom
2006-09-17 19:13 ` Chuck Foreman
2006-09-17 19:22 ` Russ Cox
[not found] ` <ee9e417a0609171222v1163c0d5k49987948781fc714@mail.gmail.co m>
2006-09-17 20:05 ` Chuck Foreman
2006-09-17 20:33 ` Russ Cox
2006-09-17 20:40 ` John Floren
2006-09-17 21:01 ` geoff
2006-09-17 21:03 ` John Floren
2006-09-17 21:23 ` geoff
2006-09-17 21:10 ` Bruce Ellis [this message]
2006-09-17 21:18 ` erik quanstrom
2006-09-17 21:20 ` Bruce Ellis
2006-09-17 23:32 ` erik quanstrom
2006-09-18 1:20 ` geoff
[not found] ` <ee9e417a0609171333t228a677eh39d1db121c39ab21@mail.gmail.co m>
2006-09-17 22:35 ` Chuck Foreman
2006-09-18 3:34 ` Burton Samograd
[not found] ` <7155ede00609172034w1d7ee768paff34c7577d6178a@mail.gmail.co m>
2006-09-18 18:28 ` Chuck Foreman
2006-09-17 19:23 Chuck Foreman
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=775b8d190609171410q4dacb30bm2ed211fcf87c821b@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--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).