debian/0000755000000000000000000000000011745052036007171 5ustar debian/copyright0000644000000000000000000001260411340677141011130 0ustar This package was debianized by Chris Taylor on Thu, 06 Mar 2008 15:41:18 -0800. It was downloaded from ftp://ftp.lcp.nrl.navy.mil/pub/nuttcp/ Upstream Authors: Bill Fink Rob Scott Copyright: © 2000-2006 Bill Fink © 2003-2006 Rob Scott License: nuttcp is free, opensource software. You can redistribute it and/or modify it under the terms of Version 2 of the GNU General Public License (GPL), as published by the GNU Project (http://www.gnu.org). A copy of the license can also be found in the LICENSE file. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. On Debian systems, the complete text of the GNU General Public License Version 2 can be found in the file `/usr/share/common-licenses/GPL-2'. All files listed below have different copyright and/or license: "missing/addrinfo.h" Copyright: © 1995-1999 WIDE Project License: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. "missing/bittypes.h" and "missing/sockstorage.h" Copyright: © 1999 WIDE Project License: Released under BSD License. On Debian systems the complete text of the BSD License can be found in the file '/usr/share/common-licenses/BSD'. "missing/fakepoll.h" Copyright: © 2000-2002 Greg Parker License: This code is in the public domain and may be copied or modified without permission. "missing/getaddrinfo.c" Copyright: © 1995-1998 WIDE Project License: Released under BSD License. On Debian systems the complete text of the BSD License can be found in the file '/usr/share/common-licenses/BSD'. "missing/inet_aton.c" Copyright: © 1995-1997 Kungliga Tekniska Högskolan License: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the Kungliga Tekniska Högskolan and its contributors. 4. Neither the name of the Institute nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE INSTITUTE AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE INSTITUTE OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. "missing/inet_ntop.c" and "missing/inet_pton.c" Copyright: © 1999 Kungliga Tekniska Högskolan License: Same as "missing/inet_aton.c" The Debian packaging is © 2008-2009, Chris Taylor and is licensed under the GPL. On Debian systems, the complete text of the GNU General Public License can be found in the file `/usr/share/common-licenses/GPL'. debian/patches/0000755000000000000000000000000011340677140010620 5ustar debian/patches/02-xinetd.d0000644000000000000000000000167511340677140012510 0ustar Fix xinetd scripts so that they will work properly with the Debian package. Author: Chris Taylor --- nuttcp-5.5.5.orig/xinetd.d/nuttcp +++ nuttcp-5.5.5/xinetd.d/nuttcp @@ -5,7 +5,7 @@ socket_type = stream wait = no user = nobody - server = /usr/local/bin/nuttcp + server = /usr/bin/nuttcp server_args = -S log_on_failure += USERID disable = yes --- nuttcp-5.5.5.orig/xinetd.d/nuttcp4 +++ nuttcp-5.5.5/xinetd.d/nuttcp4 @@ -6,7 +6,7 @@ socket_type = stream wait = no user = nobody - server = /usr/local/bin/nuttcp + server = /usr/bin/nuttcp server_args = -S -4 log_on_failure += USERID disable = yes --- nuttcp-5.5.5.orig/xinetd.d/nuttcp6 +++ nuttcp-5.5.5/xinetd.d/nuttcp6 @@ -7,7 +7,7 @@ socket_type = stream wait = no user = nobody - server = /usr/local/bin/nuttcp + server = /usr/bin/nuttcp server_args = -S -6 log_on_failure += USERID disable = yes debian/patches/00-Makefile0000644000000000000000000000161511340677140012500 0ustar Patch Makefile so that nuttcp will build sanely on Debian systems. Author: Chris Taylor --- a/Makefile +++ b/Makefile @@ -1,8 +1,8 @@ -APP = nuttcp-6.1.2 -#EXTRAVERSION=-pre1 +DESTDIR= +EXTRAVERSION= +APP = nuttcp CC = gcc -Wall -#OPT = -g -O0 -OPT = -O3 +OPT = -g -O2 CFLAGS = $(OPT) $(NOIPV6) LIBS = ifneq ($(NOIPV6),) @@ -69,3 +69,10 @@ clean: tar: (cd ..; $(TAR) cfj $(APP)$(EXTRAVERSION).tar.bz2 --exclude $(APP)/bin --exclude $(APP)/cygwin/*.bz2 --exclude $(APP)/rpm $(APP)$(EXTRAVERSION)$(APPEXT)) (cd ..; $(TAR) cfj $(APP)$(EXTRAVERSION).rpm.tar.bz2 --exclude $(APP)/bin --exclude $(APP)/cygwin --exclude $(APP)/missing --exclude $(APP)/rpm $(APP)$(EXTRAVERSION)$(APPEXT)) + +install: + mkdir -p ${DESTDIR}/usr/bin + install -m 0755 nuttcp ${DESTDIR}/usr/bin/nuttcp + mkdir -p ${DESTDIR}/usr/share/man/man8/ + install -m 0644 nuttcp.8 ${DESTDIR}/usr/share/man/man8/ + debian/patches/01-Man0000644000000000000000000003010511340677140011473 0ustar Fix manpage so that it is lintian clean and sane. Author: Chris Taylor < --- nuttcp-5.5.5.orig/nuttcp.8 +++ nuttcp-5.5.5/nuttcp.8 @@ -7,11 +7,11 @@ .ie \\n(.$-1 .RI "[\ \fB\\$1\fP" "\\$2" "\ ]" .el .RB "[\ " "\\$1" "\ ]" .. -.B nuttcp -h +.B nuttcp \-h .br -.B nuttcp -V +.B nuttcp \-V .br -.B nuttcp -t +.B nuttcp \-t .OP \-bdDsuv .OP \-c dscp_value .OP \-l buffer_len @@ -38,7 +38,7 @@ .I input ] .br -.B nuttcp -r +.B nuttcp \-r .OP \-bBdsuv .OP \-c dscp_value .OP \-l buffer_len @@ -67,10 +67,10 @@ .I output ] .br -.B nuttcp -S +.B nuttcp \-S .OP \-P control_port .br -.B nuttcp -1 +.B nuttcp \-1 .OP \-P control_port .ad .SH DESCRIPTION @@ -103,21 +103,21 @@ There are two basic modes of operation for nuttcp. The original or classic mode is the transmitter/receiver mode, which is also the way the original ttcp and nttcp worked. In this mode, a receiver is first -initiated on the destination host using "nuttcp -r", and then a -transmitter must be started on the source host using "nuttcp -t". +initiated on the destination host using "nuttcp \-r", and then a +transmitter must be started on the source host using "nuttcp \-t". This mode is somewhat deprecated and is no longer recommended for general use. The preferred and recommended mode of operation for nuttcp is the new client/server mode. With this mode, a server is -first started on one system using "nuttcp -S" (or "nuttcp -1"), -and then a client may either transmit data to (using "nuttcp -t") -or receive data from (using "nuttcp -r") the server system. All +first started on one system using "nuttcp \-S" (or "nuttcp \-1"), +and then a client may either transmit data to (using "nuttcp \-t") +or receive data from (using "nuttcp \-r") the server system. All the information provided by nuttcp is reported by the client, including the information from the server, thus providing a full snapshot of both the transmitter and receiver ends of the data transfer. .PP The server may be started by a normal, non-privileged user by issuing -either a "nuttcp -S" or a "nuttcp -1" command. However, the optimal -and recommended method of running a server is to run "nuttcp -S" via +either a "nuttcp \-S" or a "nuttcp \-1" command. However, the optimal +and recommended method of running a server is to run "nuttcp \-S" via the inetd/xinetd daemon. This method has several significant advantages, including being more robust, allowing multiple simultaneous connections, and providing for access control over who is allowed to use the nuttcp @@ -138,14 +138,14 @@ (server). .PP Normally, a nuttcp data transfer is memory-to-memory. However, by -using the "-s" option, it is possible to also perform memory-to-disk, -disk-to-memory, and disk-to-disk data transfers. Using the "-s" option +using the "\-s" option, it is possible to also perform memory-to-disk, +disk-to-memory, and disk-to-disk data transfers. Using the "\-s" option with the transmitter will cause nuttcp to read its data from the standard input instead of using a prefabricated memory buffer, -while using the "-s" option on the receiver causes nuttcp to write +while using the "\-s" option on the receiver causes nuttcp to write its data to standard output. All these types of data transfers are possible with the classic transmitter/receiver mode. For security -reasons, the "-s" option is disabled on the server, so it is not +reasons, the "\-s" option is disabled on the server, so it is not possible to access the disk on the server side of a data transfer. .PP The allowed options to nuttcp are: @@ -157,7 +157,7 @@ .TP .B \-V Prints the nuttcp version number. The nuttcp version is also printed -as part of the normal nuttcp output when the "-v" verbose output is +as part of the normal nuttcp output when the "\-v" verbose output is used (but not when using the default brief output). In client/server mode, the version number of both the client and server is identified. .TP @@ -175,7 +175,7 @@ .TP .B \-S Indicates that this nuttcp is the server. The only option that may -be specified to the server is the "-P" option, which allows one to +be specified to the server is the "\-P" option, which allows one to change the control port used by the server, but only when the server is started by a normal, non-privileged user. When the server is initiated by inetd/xinetd, the server control port should be specified @@ -184,13 +184,13 @@ file. .TP .B \-1 -Basically the same as the "-S" option, but indicates a one-shot server, +Basically the same as the "\-S" option, but indicates a one-shot server, i.e. the server exits after the first data transfer initiated by a -client. The "-1" option should only be used when the server is started +client. The "\-1" option should only be used when the server is started by a normal, non-privileged user. This option will probably rarely need to be used, but can be useful for a quick test and eliminates the possibilty of leaving a non-access controlled nuttcp server running -on the system (which can happen when using the "-S" option and forgetting +on the system (which can happen when using the "\-S" option and forgetting to kill the nuttcp server after finishing a series of tests). .TP .B \-b @@ -204,11 +204,11 @@ .TP .B \-B This option is only valid for the receiver, and forces the receiver -to read a full buffer (as specified by the "-l" buffer length option) -from the network. It is mainly intended to be used with the "-s" +to read a full buffer (as specified by the "\-l" buffer length option) +from the network. It is mainly intended to be used with the "\-s" option to only output full buffers to standard output (e.g. for use with tar). It is also implicitly set whenever the number of streams -as specified by the "-N" option is greater than 1. This option is +as specified by the "\-N" option is greater than 1. This option is not passed to the server. .TP .B \-d @@ -225,10 +225,10 @@ which may possibly be removed or renamed in a future version of nuttcp. .TP .B \-s -Setting the "-s" option causes nuttcp to either read its data from +Setting the "\-s" option causes nuttcp to either read its data from standard input rather than using prefabricated memory buffers (for -"nuttcp -t"), or to write its data out to standard output (for -"nuttcp -r"). The "-s" option is disabled for security reasons +"nuttcp \-t"), or to write its data out to standard output (for +"nuttcp \-r"). The "\-s" option is disabled for security reasons on the server. .TP .B \-u @@ -237,8 +237,8 @@ .B \-v Verbose output that provides some additional information related to the data transfer. In client/server mode, the server is always verbose -(implicit "-v" option), but the client controls the extent and type of -output via the "-v" and "-b" options. +(implicit "\-v" option), but the client controls the extent and type of +output via the "\-v" and "\-b" options. .TP .BI \-c dscp_value Sets the socket option to support COS. Either takes a dscp value or @@ -253,14 +253,14 @@ .BI \-n num_bufs Specifies the number of source buffers written to the network (default is unlimited), and is ignored by the receiver. For client/server -mode, if the client issues a "nuttcp -r" command making it the +mode, if the client issues a "nuttcp \-r" command making it the receiver, this parameter is passed to the server since the server is the transmitter in this case. This parameter is also ignored -if the "-s" parameter is specified to the transmitter. +if the "\-s" parameter is specified to the transmitter. .TP .BI \-w window_size -Indicates the window size in KB of the transmitter (for "nuttcp -t") -or receiver (for "nuttcp -r"). Actually, to be technically correct, +Indicates the window size in KB of the transmitter (for "nuttcp \-t") +or receiver (for "nuttcp \-r"). Actually, to be technically correct, it sets the sender or receiver TCP socket buffer size, which then effectively sets the window size. For client/server mode, both the transmitter and receiver window sizes are set. The default window @@ -273,14 +273,14 @@ but less than the doubled value set by Linux. .TP .BI \-ws server_window -For client/server mode, the "-ws" option provides a mechanism for +For client/server mode, the "\-ws" option provides a mechanism for setting a different window size on the server than the client window -size as specified with the "-w" option. +size as specified with the "\-w" option. .TP .B \-wb Normally, to conserve memory, the transmitter only sets the TCP send socket buffer size and the receiver only sets the TCP receive socket -buffer size. However, if the "-wb" option is used, the transmitter +buffer size. However, if the "\-wb" option is used, the transmitter will also set the TCP receive socket buffer size and the receiver will also set the TCP send socket buffer size. Under normal circumstances, this should never be necessary. This option was implemented because @@ -291,7 +291,7 @@ .TP .BI \-p data_port Port number used for the data connection, which defaults to port 5001. -If multiple streams are specified with the "-N" option, the "-p" option +If multiple streams are specified with the "\-N" option, the "\-p" option specifies the starting port number for the data connection. For example, if four streams are specified using the default data connection port number, nuttcp will use ports 5001, 5002, 5003, and 5004 for the four @@ -300,7 +300,7 @@ .BI \-P control_port For client/server mode, specifies the port number used for the control connection between the client and server, and defaults to port 5000. -On the server side, the "-P" option should only be used when the server +On the server side, the "\-P" option should only be used when the server is started manually by the user. If the server is started by inetd/xinetd (the preferred method), the control connection must be specified by adding a nuttcp entry to the @@ -311,7 +311,7 @@ Species the number of parallel TCP (or UDP) data streams to be used for the data transfer, with the default being a single data stream. The maximum number of parallel data streams that can be used is 128. If the -number of streams is greater than one, the "-B" option is implicitly set. +number of streams is greater than one, the "\-B" option is implicitly set. The current implementation does not fork off separate processes for each data stream, so specifying multiple streams on an SMP machine will not take advantage of its multiple processors. Of course it is always possible @@ -319,7 +319,7 @@ if there is any advantage to running on multiple processors. This is especially simple to do when running in client/server mode when the server is started from the inetd/xinetd daemon. When running multiple nuttcp -commands in parallel, the "-T" transmitter timeout option may be used +commands in parallel, the "\-T" transmitter timeout option may be used to insure that all the nuttcp commands finish at approximately the same time. .TP @@ -335,7 +335,7 @@ time, so if nuttcp is switched out of the processor for any reason, when it is switched back in, it is possible that the instantaneous rate may momentarily exceed the specified value. There is an 'i' qualifier to -the rate limit option (specified as "-Ri") that will restrict the +the rate limit option (specified as "\-Ri") that will restrict the instantaneous rate at any given point in time to the specified value, although in this case the final rate reported by nuttcp may be less than the specified value since nuttcp won't attempt to catch up if other @@ -347,8 +347,8 @@ Limits the amount of time that the transmitter will send data to the specified number of seconds, or number of minutes if the 'm' suffix is used. Normally a data transfer will either specify a fixed amount -of data to send using the "-n" option, or a fixed period of time to -send using the "-T" option. However, if both the "-n" and "-T" options +of data to send using the "\-n" option, or a fixed period of time to +send using the "\-T" option. However, if both the "\-n" and "\-T" options are used, the data transfer will be stopped by whichever option takes affect first. The default is a 10 second time limit for the data transfer. debian/patches/04-Spelling0000644000000000000000000000061111340677140012537 0ustar Fixes a spelling error. Author: Chris Taylor --- a/nuttcp-6.1.2.c +++ b/nuttcp-6.1.2.c @@ -5894,7 +5894,7 @@ getoptvalp( char **argv, int index, int #define NETSTAT "netstat" #if defined(linux) -#define RETRANS "segments retransmited" +#define RETRANS "segments retransmitted" #define NETSTAT_DIR "/bin/" #define NRETRANS_BEFORE #elif defined(__FreeBSD__) debian/patches/03-IPv60000644000000000000000000000040011340677140011541 0ustar Make nuttcp build with IPv6 support. Author: Chris Taylor --- a/Makefile +++ b/Makefile @@ -6,7 +6,7 @@ OPT = -g -O2 CFLAGS = $(OPT) $(NOIPV6) LIBS = ifneq ($(NOIPV6),) -APPEXTV6=-noipv6 +APPEXTV6= endif APPEXT = $(APPEXTV6) debian/patches/series0000644000000000000000000000006311340677140012034 0ustar 00-Makefile 01-Man 02-xinetd.d 03-IPv6 04-Spelling debian/control0000644000000000000000000000126111745051455010600 0ustar Source: nuttcp Section: net Priority: extra Maintainer: Chris Taylor Build-Depends: debhelper (>= 9) Standards-Version: 3.9.3 Package: nuttcp Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} Description: network performance measurement tool nuttcp is a network performance measurement tool intended for use by network and system managers. Its most basic usage is to determine the raw TCP (or UDP) network layer throughput by transferring memory buffers from a source system across an interconnecting network to a destination system, either transferring data for a specified time interval, or alternatively transferring a specified number of bytes. debian/dirs0000644000000000000000000000001011340677141010045 0ustar usr/bin debian/source/0000755000000000000000000000000011745046763010503 5ustar debian/source/format0000644000000000000000000000001411340677141011700 0ustar 3.0 (quilt) debian/rules0000755000000000000000000000003611745051466010256 0ustar #!/usr/bin/make -f %: dh $@ debian/examples0000644000000000000000000000006211340677141010731 0ustar xinetd.d/nuttcp xinetd.d/nuttcp4 xinetd.d/nuttcp6 debian/compat0000644000000000000000000000000211745046703010373 0ustar 9 debian/README.source0000644000000000000000000000041611340677141011352 0ustar There are no special requirements needed to build nuttcp from source. It uses the quilt patch system, which you can find information about on Debian systems at '/usr/share/doc/quilt/README.source.' -- Chris Taylor Sun, 06 Dec 2009 16:48:37 -0700 debian/docs0000644000000000000000000000002411340677141010041 0ustar examples.txt README debian/changelog0000644000000000000000000000356611745051513011054 0ustar nuttcp (6.1.2-4) unstable; urgency=low * Bump standards-version. * Bump compat version. * Remove build-dep on quilt. * Fix option ordering for dh in debian/rules. -- Chris Taylor Sun, 22 Apr 2012 18:27:46 +0000 nuttcp (6.1.2-3) unstable; urgency=low * Used minimal dh7 instead of cdbs and removed cdbs build-dep. * Updated my email address. * Updated debian/copyright. * Fixed a spelling error in nuttcp in 04-Spelling. * Fixed grammatical errors in debian/README.source. -- Chris Taylor Mon, 07 Dec 2009 00:42:18 +0000 nuttcp (6.1.2-2) unstable; urgency=low * Bump standards-version. * Add debian/README.source. * Remove nuttcp.html from debian/docs. -- Chris Taylor Wed, 19 Aug 2009 00:48:29 +0000 nuttcp (6.1.2-1) unstable; urgency=low * New upstream release. * Bump standards-version. * Add descriptions to patches. * Fix copyright symbols in debian/copyright. * Fix 00-Makefile and 03-IPv6 so that they will apply correctly. * Fix debian/watch. -- Chris Taylor Wed, 20 May 2009 04:54:47 +0000 nuttcp (5.5.5-3) unstable; urgency=low * Enable IPv6 in patch 03-IPv6. -- Chris Taylor Fri, 26 Sep 2008 02:02:13 +0000 nuttcp (5.5.5-2) unstable; urgency=low * Bump standards-version. * Fix quilt patches to support new source format 3.0 * Updated watch file. -- Chris Taylor Wed, 23 Sep 2008 18:13:52 +0000 nuttcp (5.5.5-1) unstable; urgency=low * Patched files in xinetd.d/ in 02-xinetd.d so that the inetd references point to the proper binary. * Patched manpage in 01-Man to correct lintian warnings. * Patched Makefile in 00-Makefile so that it will build sanely * Initial release (Closes: #463493) -- Chris Taylor Fri, 07 Mar 2008 07:14:37 +0000 debian/watch0000644000000000000000000000014311340677141010221 0ustar version=3 ftp://ftp.lcp.nrl.navy.mil/pub/nuttcp/nuttcp-([1-9].[1-9].[1-9])\.tar.bz2 debian uupdate debian/README.Debian0000644000000000000000000000036511340677141011237 0ustar nuttcp for Debian ----------------- There are some example xinetd scripts in the '/usr/share/docs/nuttcp/examples/' directory for using nuttcp as a server through inetd. -- Chris Taylor Sun, 06 Dec 2009 16:48:37 -0700