From: mkc@bull.se mkc@bull.se
Subject: 387 required? *and* Memory errors? Mothra sucks?
Date: Sat, 5 Aug 1995 04:33:01 -0400 [thread overview]
Message-ID: <19950805083301.HJ8Js5-W5oC9k_VVJouaxKuUoGiuHQPAb8QkqpXcwN4@z> (raw)
Daniel Egnor writes about Plan 9 dealing poorly with memory errors and
gives this example of rc code:
> fn ls { lc -F }
> (If you're clever you'll figure out why this loops -- it took me a while, since
> I wasn't used to the system) will very quickly cause an 8MB machine to scroll
> "No physical memory" messages all over the screen.
I did that too, under AIX, the IBM (and Bull) Unix. My rc was over 15
MB before I killed the process. Oops. The memory in the machine is 288
MB, though, so I didn't have to go through what you describe. Anyway,
it's not just Plan 9 that deals poorly with out-of-memory
situations. Look at your vanilla Unix system and see what it does...
Mikael Cardell, Dharma Hacker <mkc@bull.se>
/* No, I don't speak for Bull */
next reply other threads:[~1995-08-05 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-05 8:33 mkc [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-05 16:20 Daniel
1995-08-05 16:10 philw
1995-08-05 7:49 Steven
1995-08-05 6:33 rob
1995-08-05 5:36 Daniel
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=19950805083301.HJ8Js5-W5oC9k_VVJouaxKuUoGiuHQPAb8QkqpXcwN4@z \
--to=mkc@bull.se \
/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).