summaryrefslogtreecommitdiff
path: root/benchmarks/forkbomb
diff options
context:
space:
mode:
authorRoman Bogorodskiy <novel@FreeBSD.org>2005-05-15 18:41:36 +0000
committerRoman Bogorodskiy <novel@FreeBSD.org>2005-05-15 18:41:36 +0000
commite5ff846f71fd66c6dc650d13e0ded2b555fb6ec6 (patch)
tree49a6554d0138b5c39057fbdcb4d9e76d6c351031 /benchmarks/forkbomb
parentChange PORTNAME & DISTNAME to reflect repocopy name (diff)
Update to 1.4.
PR: 81029 Submitted by: Radim Kolar <hsn@netmag.cz>
Notes
Notes: svn path=/head/; revision=135305
Diffstat (limited to 'benchmarks/forkbomb')
-rw-r--r--benchmarks/forkbomb/Makefile5
-rw-r--r--benchmarks/forkbomb/distinfo4
-rw-r--r--benchmarks/forkbomb/pkg-descr18
3 files changed, 15 insertions, 12 deletions
diff --git a/benchmarks/forkbomb/Makefile b/benchmarks/forkbomb/Makefile
index 49ee2eb7c090..fc1381d506aa 100644
--- a/benchmarks/forkbomb/Makefile
+++ b/benchmarks/forkbomb/Makefile
@@ -6,9 +6,10 @@
#
PORTNAME= forkbomb
-PORTVERSION= 1.3
+PORTVERSION= 1.4
CATEGORIES= benchmarks
-MASTER_SITES= ${MASTER_SITE_SUNSITE}
+MASTER_SITES= ${MASTER_SITE_SUNSITE} \
+ http://home.tiscali.cz:8080/~cz210552/distfiles/
MASTER_SITE_SUBDIR= system/benchmark
MAINTAINER= ports@FreeBSD.org
diff --git a/benchmarks/forkbomb/distinfo b/benchmarks/forkbomb/distinfo
index 28114ce9805e..7bafa1fad583 100644
--- a/benchmarks/forkbomb/distinfo
+++ b/benchmarks/forkbomb/distinfo
@@ -1,2 +1,2 @@
-MD5 (forkbomb-1.3.tar.gz) = 4410e2e976aba2687bb4c29b712bacb5
-SIZE (forkbomb-1.3.tar.gz) = 4428
+MD5 (forkbomb-1.4.tar.gz) = b806797a61a46c7176857bf24597a1b8
+SIZE (forkbomb-1.4.tar.gz) = 4718
diff --git a/benchmarks/forkbomb/pkg-descr b/benchmarks/forkbomb/pkg-descr
index 753fddb51091..c65e8ce659c9 100644
--- a/benchmarks/forkbomb/pkg-descr
+++ b/benchmarks/forkbomb/pkg-descr
@@ -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