drieux <[EMAIL PROTECTED]> writes:
> On Dec 19, 2003, at 8:55 AM, Dan Anderson wrote:
> [..]
> > I'm creating an app that uses forks in a number of places to do things
> > quicker. Unfortunately, I have a bad habit of accidentally fork
> > bombing
> > my box.
>
> I'm not sure I get this phrase 'fork bombing' to begin with,
I'll do something dumb, like fork in a loop while
$number_forks < $fork_this_many. But, for whatever reasons, I have a
tendency to do things like create an infinite loop by accident, and
fork an infinite number of processes, or soemthign like that. This
results in what is effectively a DOS on my box, because it starts
swapping as soon as it eats up all the RAM and is unresponsive without
a hard reboot. :-(
Now, try as I might to prevent these, in the same way that
every once in a while I leave an infinite loop on a normal program or
do something similarly dumb, when I do it with forks I have a tendency
to eat up resources until I get DOSed. So instead of spending the 30
seconds killing the process, looking into the code, cursing myself,
and fixing it, I end up hard rebooting and recovering all my autosaved
files. :-(
-Dan
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
