From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: "David E. Fox" <dfox@belvdere.vip.best.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: fork: out of memory
Date: Thu, 4 Dec 1997 10:37:02 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.971204103425.6860D-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199712040152.RAA00762@belvdere.vip.best.com>
On Wed, 3 Dec 1997, David E. Fox wrote:
> > Was that with my patch running, or wery you trying to get it
> > in... On my own system (24Mb) I magaged to compile the kernel
> > with 'make -j5' without any problems...
>
> Without the patch, i.e., clean 2.1.65 (make bzimage though)
>
[snip]
>
> I wrote in the other message that I got it to compile OK.
> Strangely enough, it failed twice in the same spot (ide.c) which
> I haven't yet experienced. Third time though it worked.
Maybe you should compile in <magic-sysrq> support and try
<sysrq>-M when memory gets tight...
>
> Strangely enough, I haven't seen any 'cannot fork' messages
> today (yet). I got a slew of them yesterday (over 40 messages
> saying 'cannot fork'). The only real difference is that netscape
> is sitting around. Wierd.
Hmm, strange. You'd expect Netscape to grab loads of memory
so other programs could get even less... Or was it just
'sitting around' and doing nothing:)
grtz,
Rik.
----------
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...
next parent reply other threads:[~1997-12-04 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199712040152.RAA00762@belvdere.vip.best.com>
1997-12-04 9:37 ` Rik van Riel [this message]
[not found] <Pine.OSF.3.95.971127130913.4485D-100000@ruunat.fys.ruu.nl>
1997-11-27 13:35 ` Rik van Riel
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=Pine.LNX.3.91.971204103425.6860D-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=dfox@belvdere.vip.best.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox