kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/benchmarks/flowgrind/Makefile

22 lines
521 B
Makefile
Raw Normal View History

Flowgrind grinds flows among hosts in your network. It is a tool similar to iperf, netperf to measure throughput and other metrics for TCP. Flowgrind is split into two components: the flowgrind daemon and the flowgrind controller. Using the controller, flows between any two systems running the flowgrind daemon can be setup (third party tests). At regular intervals during the test the controller collects and displays the measured results from the daemons. It can run multiple flows at once with the same or different settings and individually schedule every one. Test and control connection can optionally be diverted to different interfaces. WWW: http://launchpad.net/flowgrind PR: ports/176728 Submitted by: Lars Eggert <lars@eggert.org>
2013-03-08 03:44:53 +01:00
# Created by: Lars Eggert <lars@eggert.org>
# $FreeBSD$
PORTNAME= flowgrind
- Update to version 0.6.1 - Port now links dynamically to libpcap from ports, add it to LIB_DEPENDS with ABI version to prevent detecting libpcap from base PR: ports/180756 Submitted by: Lars Eggert <lars@eggert.org> (maintainer)
2013-07-23 19:21:32 +02:00
PORTVERSION= 0.6.1
Update math/gsl to 1.16 and adjust some dependent ports
2013-08-26 18:06:37 +02:00
PORTREVISION= 1
Flowgrind grinds flows among hosts in your network. It is a tool similar to iperf, netperf to measure throughput and other metrics for TCP. Flowgrind is split into two components: the flowgrind daemon and the flowgrind controller. Using the controller, flows between any two systems running the flowgrind daemon can be setup (third party tests). At regular intervals during the test the controller collects and displays the measured results from the daemons. It can run multiple flows at once with the same or different settings and individually schedule every one. Test and control connection can optionally be diverted to different interfaces. WWW: http://launchpad.net/flowgrind PR: ports/176728 Submitted by: Lars Eggert <lars@eggert.org>
2013-03-08 03:44:53 +01:00
CATEGORIES= benchmarks
- Update to version 0.6.1 - Port now links dynamically to libpcap from ports, add it to LIB_DEPENDS with ABI version to prevent detecting libpcap from base PR: ports/180756 Submitted by: Lars Eggert <lars@eggert.org> (maintainer)
2013-07-23 19:21:32 +02:00
MASTER_SITES= https://launchpad.net/flowgrind/trunk/${PORTNAME}-0.6.1/+download/
Flowgrind grinds flows among hosts in your network. It is a tool similar to iperf, netperf to measure throughput and other metrics for TCP. Flowgrind is split into two components: the flowgrind daemon and the flowgrind controller. Using the controller, flows between any two systems running the flowgrind daemon can be setup (third party tests). At regular intervals during the test the controller collects and displays the measured results from the daemons. It can run multiple flows at once with the same or different settings and individually schedule every one. Test and control connection can optionally be diverted to different interfaces. WWW: http://launchpad.net/flowgrind PR: ports/176728 Submitted by: Lars Eggert <lars@eggert.org>
2013-03-08 03:44:53 +01:00
MAINTAINER= lars@eggert.org
COMMENT= Measure throughput and other metrics for TCP
In preparation for making libtool generate libraries with a sane name, fix all LIB_DEPENDS in benchmarks
2013-12-11 15:38:29 +01:00
LIB_DEPENDS= libxmlrpc++.so:${PORTSDIR}/net/xmlrpc-c \
libgsl.so:${PORTSDIR}/math/gsl \
- Unbreak, it seems this port wants libpcap from ports not base - Stage support Reported by: pkg-fallout
2014-02-22 18:09:47 +01:00
libpcap.so.1:${PORTSDIR}/net/libpcap
Flowgrind grinds flows among hosts in your network. It is a tool similar to iperf, netperf to measure throughput and other metrics for TCP. Flowgrind is split into two components: the flowgrind daemon and the flowgrind controller. Using the controller, flows between any two systems running the flowgrind daemon can be setup (third party tests). At regular intervals during the test the controller collects and displays the measured results from the daemons. It can run multiple flows at once with the same or different settings and individually schedule every one. Test and control connection can optionally be diverted to different interfaces. WWW: http://launchpad.net/flowgrind PR: ports/176728 Submitted by: Lars Eggert <lars@eggert.org>
2013-03-08 03:44:53 +01:00
cat astro / benchmarks - USE_(BZIP2|XZ) -> USES=tar:(bzip2|xz) - adjust BSDn License
2014-06-01 11:00:15 +02:00
USES= tar:bzip2
Flowgrind grinds flows among hosts in your network. It is a tool similar to iperf, netperf to measure throughput and other metrics for TCP. Flowgrind is split into two components: the flowgrind daemon and the flowgrind controller. Using the controller, flows between any two systems running the flowgrind daemon can be setup (third party tests). At regular intervals during the test the controller collects and displays the measured results from the daemons. It can run multiple flows at once with the same or different settings and individually schedule every one. Test and control connection can optionally be diverted to different interfaces. WWW: http://launchpad.net/flowgrind PR: ports/176728 Submitted by: Lars Eggert <lars@eggert.org>
2013-03-08 03:44:53 +01:00
GNU_CONFIGURE= yes
benchmarks/flowgrind: fix IPv6 address parsing - Fix IPv6 address parsing (upstream) - Enable debug by default PR: ports/180259 Submitted by: Lars Eggert <lars@eggert.org> (maintainer)
2013-07-05 13:53:08 +02:00
CONFIGURE_ARGS= --enable-debug
Flowgrind grinds flows among hosts in your network. It is a tool similar to iperf, netperf to measure throughput and other metrics for TCP. Flowgrind is split into two components: the flowgrind daemon and the flowgrind controller. Using the controller, flows between any two systems running the flowgrind daemon can be setup (third party tests). At regular intervals during the test the controller collects and displays the measured results from the daemons. It can run multiple flows at once with the same or different settings and individually schedule every one. Test and control connection can optionally be diverted to different interfaces. WWW: http://launchpad.net/flowgrind PR: ports/176728 Submitted by: Lars Eggert <lars@eggert.org>
2013-03-08 03:44:53 +01:00
- Update to version 0.6.1 - Port now links dynamically to libpcap from ports, add it to LIB_DEPENDS with ABI version to prevent detecting libpcap from base PR: ports/180756 Submitted by: Lars Eggert <lars@eggert.org> (maintainer)
2013-07-23 19:21:32 +02:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink