typing while :; do :; done. There are a thousand ways
No. What I write above is not a fork bomb, it's a single
process which is wasting CPU in a busy loop. It's exactly
equivalent to top(1) with zero delay, except that top
produces some output, while a busy loop does nothing useful
at
Well, an unprivileged user can achieve the same effect by
typing while :; do :; done. There are a thousand ways
to waste CPU time, and there is no way to prevent a user
from doing it.
It is not the same effect.
You describe fork bombing.
Many forked processes eat up the CPU.
I could limit
2 matches
Mail list logo
