Re: top delay value
- From: "Dr. Markus Waldeck" <waldeck@xxxxxx>
- Date: Tue, 30 Jan 2007 17:23:50 +0100
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
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: top delay value
- From: Oliver Fromme
- Re: top delay value
- From: Joerg Sonnenberger
- Re: top delay value
- References:
- Re: top delay value
- From: Oliver Fromme
- Re: top delay value
- Prev by Date: Re: top delay value
- Next by Date: Re: top delay value
- Previous by thread: Re: top delay value
- Next by thread: Re: top delay value
- Index(es):