Date: Sat, 14 May 2005 19:22:55 +0200 From: Radim Kolar <hsn@netmag.cz> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/81029: [PATCH] benchmarks/forkbomb: update to 1.4 Message-ID: <E1DX0Ln-000HfL-Kt@sanatana.dharma> Resent-Message-ID: <200505141730.j4EHU8kW053345@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 81029
>Category: ports
>Synopsis: [PATCH] benchmarks/forkbomb: update to 1.4
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Sat May 14 17:30:07 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Radim Kolar
>Release: FreeBSD 5.4-STABLE i386
>Organization:
Sanatana Dharma
>Environment:
System: FreeBSD sanatana.dharma 5.4-STABLE FreeBSD 5.4-STABLE #7: Sun May 8 12:50:59 CEST
>Description:
- Update to 1.4
- Now features `Zombies gang`
Note 1:
There may be some delay until ibiblio accepts this file.
Note 2:
FreeBSD 5.4-RELEASE do not survive forkbomb due to using
too much wired memory and then deadlocks somewhere. Do not use
on 5.4 on important machines. 5.3 and 5.2 are fine.
Generated with FreeBSD Port Tools 0.63
>How-To-Repeat:
>Fix:
--- forkbomb-1.4.patch begins here ---
diff -ruN --exclude=CVS /usr/ports/benchmarks/forkbomb/Makefile /home/hsn/myports/forkbomb/Makefile
--- /usr/ports/benchmarks/forkbomb/Makefile Mon Dec 13 18:22:08 2004
+++ /home/hsn/myports/forkbomb/Makefile Fri May 13 15:00:03 2005
@@ -6,7 +6,7 @@
#
PORTNAME= forkbomb
-PORTVERSION= 1.3
+PORTVERSION= 1.4
CATEGORIES= benchmarks
MASTER_SITES= ${MASTER_SITE_SUNSITE}
MASTER_SITE_SUBDIR= system/benchmark
diff -ruN --exclude=CVS /usr/ports/benchmarks/forkbomb/pkg-descr /home/hsn/myports/forkbomb/pkg-descr
--- /usr/ports/benchmarks/forkbomb/pkg-descr Tue Feb 3 16:09:17 2004
+++ /home/hsn/myports/forkbomb/pkg-descr Sat May 14 19:18:57 2005
@@ -1,9 +1,11 @@
-forkbomb is tool for stress testing. It can create many processes using fork(),
-allocate memory using realloc() and accesses this memory. It has
-different switches for fine-tuning operation. While classic fork() bomb is good
-only for fun, running multiple memory-eaters can be useful for determining
-maximum memory which can be given to servers (bind or squid) without taking
-machine down. You can test different operation systems with this tool and see
-how they are handling the load.
+forkbomb is tool for stress testing. It can create many processes
+using fork(), bring up some zombies, allocate memory using
+realloc() and accesses this memory. It has different switches for
+fine-tuning operation. While classic fork() bomb is good only for
+fun and QA release testing, running multiple memory-eaters can be
+useful for determining maximum memory which can be given to
+servers (bind or squid) without taking machine down. You can
+test different operation systems with this tool and see how they
+are handling the load.
-WWW: http://home.worldonline.cz/~cz210552/forkbomb.html
+WWW: http://home.tiscali.cz/~cz210552/forkbomb.html
--- forkbomb-1.4.patch ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1DX0Ln-000HfL-Kt>