From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] swap files for diskless cpu/auth servers
Date: Wed, 26 Sep 2001 10:22:36 -0400 [thread overview]
Message-ID: <200109261422.KAA25271@augusta.math.psu.edu> (raw)
In-Reply-To: <20010925174747.527EF19A05@mail.cse.psu.edu>
In article <20010925174747.527EF19A05@mail.cse.psu.edu> you write:
>Swapping works so badly in our system that its hardly
>worth turning on at all. Definitely don't waste the
>space.
Yeah, but sometimes, when recompiling the system on my diskless CPU
server with half a gig of RAM and no swap, I get an out of memory
error linking ghostscript and the build stops. If I restart it on
my laptop, which has 128 megs of RAM and however much swap space, it
works fine. Kind of a bummer.
But definately don't waste dump space for swap....
- Dan C.
next prev parent reply other threads:[~2001-09-26 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 17:47 presotto
2001-09-26 14:22 ` Dan Cross [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-25 17:34 forsyth
2001-09-28 3:21 ` Sam Ducksworth
2001-09-25 16:31 anothy
2001-09-25 16:18 Sam Ducksworth
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=200109261422.KAA25271@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).