Hello,
up till now I was convinced that a proper /etc/login.conf
provides enough protection against silly dos efforts like
fork bombs.
Well, while a hard maxproc of 64 protects very well against
echo '#!/bin/sh
a &
a &' > a; chmod 755 a; ./a
but it fails to prevent that this
main(){fork();main();}
leaves the machine in an unusable state (it does ping
back, one may break into the kernel debugger, but no
io).
Any way to prevent this (without harming the user)?
Björn
PS: Please no dispute about overcommittment or
my-fork-bomb-is-better-than-yours.
--
-----BEGIN GEEK CODE BLOCK-----
GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+
K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+
------END GEEK CODE BLOCK------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
