From: Doug McNaught <doug@wireboard.com>
To: Nico Schottelius <nicos@pcsystems.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: memory/cpu handling problem ? (x86)
Date: 05 Dec 2001 18:23:33 -0500 [thread overview]
Message-ID: <m3pu5tckui.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <3C0EA220.D943FAF6@pcsystems.de>
In-Reply-To: Nico Schottelius's message of "Wed, 05 Dec 2001 23:39:28 +0100"
Nico Schottelius <nicos@pcsystems.de> writes:
> Hello Folks!
>
> A small ansi C program which tries to get all cpu power and as much ram
> as possible got my system.
$ man setrlimit
-Doug
--
Let us cross over the river, and rest under the shade of the trees.
--T. J. Jackson, 1863
next prev parent reply other threads:[~2001-12-05 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 22:39 memory/cpu handling problem ? (x86) Nico Schottelius
2001-12-05 23:23 ` Doug McNaught [this message]
2002-03-14 9:01 ` Nico Schottelius
[not found] ` <u8elm99qsn.fsf@gromit.moeb>
2001-12-06 19:52 ` Nico Schottelius
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=m3pu5tckui.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicos@pcsystems.de \
/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