public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Sheduling + forkbomb
@ 2002-03-25 19:30 Max
  0 siblings, 0 replies; only message in thread
From: Max @ 2002-03-25 19:30 UTC (permalink / raw)
  To: Linux Kernel

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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-04-01 16:00 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-03-25 19:30 Sheduling + forkbomb Max

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox