Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Jan 2007 17:23:50 +0100
From:      "Dr. Markus Waldeck" <waldeck@gmx.de>
To:        freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de, freebsd-hackers@FreeBSD.ORG
Subject:   Re: top delay value
Message-ID:  <20070130162350.126210@gmx.net>
In-Reply-To: <200701301521.l0UFLYgE055509@lurza.secnetix.de>
References:  <200701301521.l0UFLYgE055509@lurza.secnetix.de>

next in thread | previous in thread | raw e-mail | index | archive | help
> 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 the number of process via 

:maxproc=100: \

in /etc/login.conf

> If you want to make top more secure, type "chmod 700 /usr/bin/top".

:-)

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070130162350.126210>