From: Max <ertzog@bk.ru>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Sheduling + forkbomb
Date: Mon, 25 Mar 2002 19:30:46 +0000 [thread overview]
Message-ID: <20020325193046.GA4578@bk.ru> (raw)
Isn't it strange, that a simple fork-bomb, like a command to sh:
f(){ f|f& }; f
can get machine down. I've tried several times this thing, changing
ulimit. (I've set a limit to user processes - 1000 ).
The kernel didn't want to reply even on Alt+SysRq+H.
Only Alt+SysRq+B could help. Of course, Ctrl+Alt+Del couldn't help
because init couldn't spawn processes to procees reboot scripts.
My kernel is 2.4.18
Best regards.
reply other threads:[~2002-04-01 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020325193046.GA4578@bk.ru \
--to=ertzog@bk.ru \
--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