From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: "Little, John" <JOHN.LITTLE@okdhs.org>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: fork() DoS?
Date: Fri, 22 Mar 2002 16:25:41 +0100 [thread overview]
Message-ID: <3C9B4CF5.9040303@loewe-komp.de> (raw)
In-Reply-To: <E7B0663E34409F45B77EFDB62AE0E4D2022360BD@s99mail02.okdhs.org>
Little, John wrote:
> I'm really not a programmer, just learning, but was able to bring the system
> to it's knees. This is a redhat 7.2 kernel. Is there anyway of preventing
> this?
>
> #include <unistd.h>
>
> void do_fork()
> {
> pid_t p;
>
> p = fork();
> do_fork();
> }
>
> void main()
> {
> for(;;)
> do_fork();
> }
>
in bash: help ulimit
ulimit: ulimit [-SHacdflmnpstuv] [limit]
Ulimit provides control over the resources available to processes
started by the shell, on systems that allow such control. If an
option is given, it is interpreted as follows:
-S use the `soft' resource limit
-H use the `hard' resource limit
-a all current limits are reported
-c the maximum size of core files created
-d the maximum size of a process's data segment
-f the maximum size of files created by the shell
-l the maximum size a process may lock into memory
-m the maximum resident set size
-n the maximum number of open file descriptors
-p the pipe buffer size
-s the maximum stack size
-t the maximum amount of cpu time in seconds
-u the maximum number of user processes
next prev parent reply other threads:[~2002-03-22 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 15:16 fork() DoS? Little, John
2002-03-22 15:24 ` Philip R. Auld
2002-03-22 15:25 ` Peter Wächtler [this message]
2002-03-23 22:09 ` Erik Tews
2002-03-24 16:23 ` Mark Mielke
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=3C9B4CF5.9040303@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=JOHN.LITTLE@okdhs.org \
--cc=linux-kernel@vger.kernel.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