* Bjoern Fischer <[EMAIL PROTECTED]> [000410 01:15] wrote:
> 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)?
Please reread the documentation on limits.
cputime unlimited
filesize unlimited
datasize 256MB <-
stacksize 64MB <-
coredumpsize unlimited
memoryuse unlimited
memorylocked unlimited
maxproc 4115
descriptors 8232
sockbufsize unlimited
If appropriate limits are in place and you still get problems
then let us know.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
