netperf Manual

A PDF version of this document is available here.

OpenSS7 NETPERF Utility

OpenSS7 NETPERF Utility Installation and Reference Manual

About This Manual

This is Edition 7, last updated 2008-10-31, of The OpenSS7 NETPERF Utility Installation and Reference Manual, for Version 2.3 release 7 of the OpenSS7 NETPERF Utility package.

Preface

Notice

This version of netperf is a version modified by The OpenSS7 Project to support network performance testing and benchmarking of the OpenSS7 Linux Kernel Native and STREAMS implementations of Stream Control Transmission Protocol (SCTP) as described in RFC 2960. To support testing of the emerging SCTP protocol, specific stream, request/response and connect/close tests were added to test the SCTP protocol in a fashion similar to Transmission Control Protocol (TCP). The objective of retaining as much compatibility as possible to the TCP tests was to provide a basis for comparison between TCP and SCTP implementations on the Linux and HP-UX operating systems.

In addition, XTI tests have been enhanced and are used to test the OpenSS7 STREAMS XTI INET implementation, See OpenSS7 STREAMS INET Driver. The OpenSS7 STREAMS INET implementation is an implementation XTI STREAMS over Sockets for the Linux operating system. Tests in the XTI API test group compared against equivalent tests in the Sockets API test group provide an indication of the overheads introduced by running XTI over Sockets. The OpenSS7 STREAMS INET driver also provides XTI over Sockets for the Linux Native SCTP implementation and comparisons between the XTI over Sockets and pure STREAMS approaches to SCTP can be made.

Abstract

This manual provides a Installation and Reference Manual for OpenSS7 NETPERF Utility.

Objective

The objective of this manual is to provide a guide for the STREAMS programmer when developing STREAMS modules, drivers and application programs for OpenSS7 NETPERF Utility.

This guide provides information to developers on the use of the STREAMS mechanism at user and kernel levels.

STREAMS was incorporated in UNIX System V Release 3 to augment the character input/output (I/O) mechanism and to support development of communication services.

STREAMS provides developers with integral functions, a set of utility routines, and facilities that expedite software design and implementation.

Intent

The intent of this manual is to act as an introductory guide to the STREAMS programmer. It is intended to be read alone and is not intended to replace or supplement the OpenSS7 NETPERF Utility manual pages. For a reference for writing code, the manual pages (see STREAMS(9)) provide a better reference to the programmer. Although this describes the features of the OpenSS7 NETPERF Utility package, OpenSS7 Corporation is under no obligation to provide any software, system or feature listed herein.

Audience

This manual is intended for a highly technical audience. The reader should already be familiar with Linux kernel programming, the Linux file system, character devices, driver input and output, interrupts, software interrupt handling, scheduling, process contexts, multiprocessor locks, etc.

The guide is intended for network and systems programmers, who use the STREAMS mechanism at user and kernel levels for Linux and UNIX system communication services.

Readers of the guide are expected to possess prior knowledge of the Linux and UNIX system, programming, networking, and data communication.

Revisions

Take care that you are working with a current version of this manual: you will not be notified of updates. To ensure that you are working with a current version, contact the Author, or check The OpenSS7 Project website for a current version.

A current version of this manual is normally distributed with the OpenSS7 NETPERF Utility package, netperf-2.3.7.¹

Version Control

     netperf.texi,v
     Revision 0.9.2.19  2008-09-20 11:04:24  brian
     - added package patchlevel
     
     Revision 0.9.2.18  2008-08-03 06:03:27  brian
     - protected agains texinfo commands in log entries
     
     Revision 0.9.2.17  2008-04-25 11:50:43  brian
     - updates to AGPLv3
     
     Revision 0.9.2.16  2007/08/12 06:43:48  brian
     - updated licenses in manuals
     
     Revision 0.9.2.15  2007/02/28 06:30:21  brian
     - updates and corrections, #ifdef instead of #if
     
     Revision 0.9.2.14  2006/09/18 01:06:18  brian
     - updated manuals and release texi docs
     
     Revision 0.9.2.13  2006/08/28 10:46:52  brian
     - correction
     
     Revision 0.9.2.12  2006/08/28 10:32:43  brian
     - updated references
     
     Revision 0.9.2.11  2006/08/27 12:26:32  brian
     - finalizing auto release files
     
     Revision 0.9.2.10  2006/08/26 18:31:36  brian
     - handle long urls
     
     Revision 0.9.2.9  2006/08/26 09:16:18  brian
     - better release file generation
     
     Revision 0.9.2.8  2006/08/23 11:00:25  brian
     - added preface, corrections and updates for release
     
     Revision 0.9.2.6  2006-03-22 03:01:58 -0700  brian
     - added makefile target index
     
     Revision 0.9.2.5  2006-03-03 04:56:43 -0700  brian
     - 64-bit compatibility
     
     Revision 0.9.2.4  2005-07-08 07:15:37 -0600  brian
     - updates to documentation
     
     Revision 0.9.2.3  2005-07-01 01:29:37 -0600  brian
     - updates for LE2005 build
     
     Revision 0.9.2.2  2005-06-24 07:38:58 -0600  brian
     - added troubleshooting section to manuals
     
     Revision 0.9.2.1  2005-05-30 02:44:01 -0600  brian
     - moved documentation for RHEL4 build
     
     Revision 0.9  2005-05-30 02:44:01 -0600  brian
     file netperf.texi was initially added on branch HP.

ISO 9000 Compliance

Only the TeX, texinfo, or roff source for this manual is controlled. An opaque (printed, postscript or portable document format) version of this manual is an UNCONTROLLED VERSION.

Disclaimer

OpenSS7 Corporation disclaims all warranties with regard to this documentation including all implied warranties of merchantability, fitness for a particular purpose, non-infringement, or title; that the contents of the manual are suitable for any purpose, or that the implementation of such contents will not infringe on any third party patents, copyrights, trademarks or other rights. In no event shall OpenSS7 Corporation be liable for any direct, indirect, special or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with any use of this manual or the performance or implementation of the contents thereof.

OpenSS7 Corporation reserves the right to revise this software and documentation for any reason, including but not limited to, conformity with standards promulgated by various agencies, utilization of advances in the state of the technical arts, or the reflection of changes in the design of any techniques, or procedures embodied, described, or referred to herein. OpenSS7 Corporation is under no obligation to provide any feature listed herein.

U.S. Government Restricted Rights

If you are licensing this Software on behalf of the U.S. Government ("Government"), the following provisions apply to you. If the Software is supplied by the Department of Defense ("DoD"), it is classified as "Commercial Computer Software" under paragraph 252.227-7014 of the DoD Supplement to the Federal Acquisition Regulations ("DFARS") (or any successor regulations) and the Government is acquiring only the license rights granted herein (the license rights customarily provided to non-Government users). If the Software is supplied to any unit or agency of the Government other than DoD, it is classified as "Restricted Computer Software" and the Government's rights in the Software are defined in paragraph 52.227-19 of the Federal Acquisition Regulations ("FAR") (or any successor regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the NASA Supplement to the FAR (or any successor regulations).

Acknowledgements

As with most open source projects, this project would not have been possible without the valiant efforts and productive software of the Free Software Foundation and the Linux Kernel Community.

Contributors

The primary contributor to the OpenSS7 OpenSS7 NETPERF Utility package is Brian F. G. Bidulock. The following is a list of significant contributors to The OpenSS7 Project:

	− Per Berquist
	− John Boyd
	− Chuck Winters
	− Peter Courtney
	− Tom Chandler
	− Gurol Ackman
	− Kutluk Testicioglu
	− John Wenker
	− Others

Authors

The authors of the OpenSS7 OpenSS7 NETPERF Utility package include:

− Brian Bidulock

See Author Index, for a complete listing and cross-index of authors to sections of this manual.

Maintainer

The maintainer of the OpenSS7 OpenSS7 NETPERF Utility package is:

− Brian Bidulock

Please send bug reports to bugs@openss7.org using the send-pr script included in the package, only after reading the BUGS file in the release, or See Problem Reports.

Web Resources

The OpenSS7 Project provides a website dedicated to the software packages released by the OpenSS7 Project.

Bug Reports

Please send bug reports to bugs@openss7.org using the send-pr script included in the OpenSS7 NETPERF Utility package, only after reading the BUGS file in the release, or See Problem Reports. You can access the OpenSS7 GNATS database directly via the web, however, the preferred method for sending new bug reports is via mail with the send-pr script.

Mailing Lists

The OpenSS7 Project provides a number of general discussion Mailing Lists for discussion concerning the OpenSS7 OpenSS7 NETPERF Utility package as well as other packages released by The OpenSS7 Project.

These are mailman mailing lists and so have convenient web interfaces for subscribers to control their settings. See http://www.openss7.org/mailinglist.html.

The mailing lists are as follows:

openss7: The openss7 mailing list is for general enquiries, information exchange and announcements regarding the OpenSS7 Project. This is our original mailing list and takes the highest amount of traffic.
openss7-announce: The openss7-announce mailing list is for announcements related to the OpenSS7 Project. This list will accept announcements posted by subscribers. Subscribe to this list if you are interested in announcements from the OpenSS7 Project, subscribers and sponsors, related to the OpenSS7 Project or STREAMS, SS7, SIGTRAN or SCTP in general.
openss7-cvs: The openss7-cvs mailing list is for automatic CVS log reporting. You must get permission of the owner to subscribe to this list. Subscribers are not allowed to post to this list, this is merely for distributing notification of changes to the CVS repository.h
openss7-develop: The openss7-develop mailing list is for email exchange related to the development projects under the OpenSS7 Project. This includes development requests, proposals, requests for comment or proposal. Subscribe to this list if you are interested in ongoing development details regarding the OpenSS7 Project.
openss7-test: The openss7-test mailing list is for email exchange related to the testing of code under the OpenSS7 Project. This specifically relates to conformance testing, verification testing, interoperability testing and beta testing. Subscribe to this list if you are interested in participating in and receiving ongoing details of test activities under the OpenSS7 Project.
openss7-bugs: The openss7-bugs mailing list is specifically tailored to bug tracking. The mailing list takes a feed from the OpenSS7 GNATS bug tracking system and accepts posting of responses to bug reports, tracking and resolution. Subscribe to this list if you are interested in receiving detailed OpenSS7 release code bug tracking information. This list is not archived; for historical information on problem reports, see our GNATS databases.
openss7-updates: The openss7-updates mailing list provides updates on OpenSS7 Project code releases and ongoing activities. Subscribers are not allowed to post to this list; this list is for official OpenSS7 Project announcements only. Subscribe to this list if you are interested in receiving updates concerning official releases and activities of the OpenSS7 Project.
openss7-streams: The openss7-streams mailing list is for email exchange related to the STREAMS development projects under the OpenSS7 Project. This includes development requests, proposals, requests for comment or proposal. Subscribe to this list if you are interested in ongoing development details regarding the OpenSS7 Project STREAMS components.
linux-streams: The linux-streams mailing list is for mail exchange related to Linux Fast-STREAMS or Linux STREAMS. This includes patches, development requests, proposals, requests for comment or proposal. Subscribe to this list if you are interested in ongoing development details regarding the STREAMS for Linux components. This is the the new (September 2006) home of the linux-streams list formerly of <gsyc.escet.urjc.es>.

Spam

To avoid spam being sent to the members of the OpenSS7 mailing list(s), we have blocked mail from non-subscribers. Please subscribe to the mailing list before attempting to post to them. (Attempts to post when not subscribed get bounced.)

As an additional measure against spam, subscriber lists for all OpenSS7 mailing lists are not accessible to non-subscribers; for most lists subscriber lists are only accessible to the list administrator. This keeps your mailing address from being picked off our website by bulk mailers.

Acceptable Use Policy

It is acceptable to post professional and courteous messages regarding the OpenSS7 package or any general information or questions concerning STREAMS, SS7, SIGTRAN, SCTP or telecommunications applications in general.

Large Attachments

The mailing list is blocked from messages of greater than 40k. If you have attachments (patches, test programs, etc.) and you mail them to the list, it will bounce to the list administrator. If you are interested in making your patches, test programs, test results or other large attachments available to the members of the mailing list, state in the message that you would like them posted and the list administrator will place them in the mail archives.

Quick Start Guide

OpenSS7 NETPERF Utility

Package netperf-2.3.7 was released under AGPLv3 2008-10-31.

Netperf is a general purpose tool for benchmarking bandwidth and performance of the Internet Protocol suite. The OpenSS7 Modified OpenSS7 NETPERF Utility package is an OpenSS7 Project release of the of the Hewlett-Packard netperf package configured to run with OpenSS7 STREAMS SCTP (Stream Control Transmission Protocol) and the OpenSS7 STREAMS XNS, XTI/TLI and INET packages.

The OpenSS7 NETPERF Utility package provide primarily the netperf(1) and netserver(8), C Language programs that act as Netperf client or server for testing connections and networking. The netserver(8) program is executed on one host acting as a server, and then netperf(1) is executed on another host acting in client mode. Characteristics of the connection or association can be altered when formed. Reporting formats and sample intervals can also be altered when the connection or association is formed. Users executing netperf(1) do not need to have shell access to the netserver(8) host.

This is a fork of the Netperf package released by Hewlett-Packard modified by the OpenSS7 Project for use with OpenSS7 STREAMS XNS, XTI/TLI, INET and SCTP packages. This OpenSS7 release of the package is based on the Netperf-2.3 release from Hewlett-Packard.

Modifications to the package are derived from the OpenSS7 STREAMS XNS, XTI/TLI, INET and SCTP implementations and are released under the GNU Affer General Public License (AGPL) Version 3. The Netperf tool itself is licensed under specific terms by Hewlett-Packard. Please see file LICENSES for the Hewlett-Packard Netperf copyright notices and licensing restrictions. The Netperf tool is

Copyright © 1993, 1994, 1995 Hewlett-Packard Company
All Rights Reserved

See the Hewlett-Packard License in the LICENSES file for complete details.

Please note that this modified version of the Netperf package is not endorsed by Hewlett-Packard in any way and that neither the original copyright holders nor OpenSS7 Corporation will take any responsibility in it.

This distribution is only currently applicable to Linux 2.4 and 2.6 kernels and was targeted at ix86, x86_64, ppc and ppc64 architectures, but should build and install for other architectures as well.

Release

This is the netperf-2.3.7 package, released 2008-10-31. This ‘2.3.7’ release, and the latest version, can be obtained from the download area of The OpenSS7 Project website using a command such as:

     $> wget http://www.openss7.org/tarballs/netperf-2.3.7.tar.bz2

The release is available as an autoconf(1) tarball, src.rpm or dsc, as a set of binary rpms or debs, or as a yum(8) or apt(8) repository. See the download page for the autoconf(1) tarballs, src.rpms, dscs, or repository access instructions. See the netperf package page for tarballs, source and binary packages.

Please see the NEWS file for release notes and history of user visible changes for the current version, and the ChangeLog file for a more detailed history of implementation changes. The TODO file lists features not yet implemented and other outstanding items.

Please see the INSTALL, INSTALL-netperf and README-make, files (or see Installation) for installation instructions.

When working from cvs(1) or git(1), please see the README-cvs, file (or see Downloading from CVS). An abbreviated installation procedure that works for most applications appears below.

This release of the package is published strictly under Version 3 of the GNU Affero Public License which can be found in the file COPYING. Package specific licensing terms (if any) can be found in the file LICENSES. Please respect these licensing arrangements. If you are interested in different licensing terms, please contact the copyright holder, or OpenSS7 Corporation <sales@openss7.com>.

See README-alpha (if it exists) for alpha release information.

Prerequisites

The quickest and easiest way to ensure that all prerequisites are met is to download and install this package from within the OpenSS7 Master Package, openss7-0.9.2.G, instead of separately.

Prerequisites for the OpenSS7 NETPERF Utility package are as follows:

Linux distribution, somewhat Linux Standards Base compliant, with a 2.4 or 2.6 kernel and the appropriate tool chain for compiling out-of-tree kernel modules. Most recent Linux distributions are usable out of the box, but some development packages must be installed. For more information, see Compatibility.

	− A fairly LSB compliant GNU/Linux distribution.²
	− Linux 2.4 kernel (2.4.10 - 2.4.27), or
	− Linux 2.6 kernel (2.6.3 - 2.6.26);
	− glibc2 or better.
	− GNU groff (for man pages).³
	− GNU texinfo (for info files).

(Note: If you acquired netperf a part of the OpenSS7 Master Package, then the dependencies listed below will already have been met by unpacking the master package.)

OpenSS7 Linux Fast-STREAMS, streams-0.9.2.4. ⁴
OpenSS7 STREAMS Compatibility Modules, strcompat-0.9.2.7.
OpenSS7 STREAMS XNS, strxns-0.9.2.7.
OpenSS7 STREAMS XTI/TLI, strxnet-0.9.2.12.
OpenSS7 STREAM Network Services Library, strnsl-0.9.2.4. (Optional.)
OpenSS7 STREAMS INET, strinet-0.9.2.7.
OpenSS7 STREAMS SCTP, strsctp-0.9.2.9.
OpenSS7 STREAMS Channels, strchan-0.9.2.4.
OpenSS7 STREAMS X.25, strx25-0.9.2.1.
OpenSS7 STREAMS ISO, striso-0.9.2.4.
OpenSS7 STREAMS ISDN, strisdn-0.9.2.4.
OpenSS7 STREAMS SS7, strss7-0.9a.8.
OpenSS7 STREAMS SIGTRAN, sigtran-0.9.2.4.
OpenSS7 STREAMS VoIP, strvoip-0.9.2.4.

When configuring and building multiple OpenSS7 Project release packages, place all of the source packages (unpacked tarballs) at the same directory level and all build directories at the same directory level (e.g. all source packages under /usr/src).

When installing packages that install as kernel modules, it is necessary to have the correct kernel development package installed. For the following distributions, use the following commands:

     Ubuntu:  $> apt-get install linux-headers
     Debian:  $> apt-get install kernel-headers
     Fedora:  $> yum install kernel-devel

You also need the same version of gcc(1) compiler with which the kernel was built. If it is not the default, add ‘CC=kgcc’ on the line after ‘./configure’, for example:

     $> ../netperf-2.3.7/configure CC='gcc-3.4'

Installation

The following commands will download, configure, build, check, install, validate, uninstall and remove the package:

     $> wget http://www.openss7.org/tarballs/netperf-2.3.7.tar.bz2
     $> tar -xjvf netperf-2.3.7.tar.bz2
     $> mkdir build
     $> pushd build
     $> ../netperf-2.3.7/configure --enable-autotest
     $> make
     $> make check
     $> sudo make install
     $> sudo make installcheck
     $> sudo make uninstall
     $> popd
     $> sudo rm -rf build
     $> rm -rf netperf-2.3.7
     $> rm -f netperf-2.3.7.tar.bz2

If you have problems, try building with the logging targets instead. If the make of a logging target fails, an automatic problem report will be generated that can be mailed to The OpenSS7 Project.⁵ Installation steps using the logging targets proceed as follows:

     $> wget http://www.openss7.org/tarballs/netperf-2.3.7.tar.bz2
     $> tar -xjvf netperf-2.3.7.tar.bz2
     $> mkdir build
     $> pushd build
     $> ../netperf-2.3.7/configure --enable-autotest
     $> make compile.log
     $> make check.log
     $> sudo make install.log
     $> sudo make installcheck.log
     $> sudo make uninstall.log
     $> popd
     $> sudo rm -rf build
     $> rm -rf netperf-2.3.7
     $> rm -f netperf-2.3.7.tar.bz2

See README-make for additional specialized make targets.

For custom applications, see the INSTALL and INSTALL-netperf files or the see Installation, as listed below. If you encounter troubles, see Troubleshooting, before issuing a bug report.

Brief Installation Instructions

The OpenSS7 NETPERF Utility package is available from the downloads area of The OpenSS7 Project website using a command such as:

     $> wget http://www.openss7.org/tarballs/netperf-2.3.7.tar.bz2

Unpack the tarball using a command such as:

     $> tar -xjvf netperf-2.3.7.tar.bz2

The tarball will unpack into the relative subdirectory named after the package name: netperf-2.3.7.

The package builds using the GNU autoconf utilities and the configure script. To build the package, we recommend using a separate build directory as follows:

     $> mkdir build
     $> cd build
     $> ../netperf-2.3.7/configure

In general, the package configures and builds without adding any special options to the configure script. For general options to the configure script, see the GNU INSTALL file in the distribution:

     $> less ../netperf-2.3.7/INSTALL

For specific options to the configure script, see the INSTALL-netperf file in the distribution, or simply execute the configure script with the --help option like so:

     $> ../netperf-2.3.7/configure --help

After configuring the package, the package can be compiled simply by issuing the ‘make’ command:

     $> make

Some specialized makefile targets exists, see the README-make file in the distribution or simply invoke the ‘help’ target like so:

     $> make help | less

After successfully building the package, the package can be checked by invoking the ‘check’ make target like so:

     $> make check

After successfully checking the package, the package can be installed by invoking the ‘install’ make target (as root) like so:

     $> sudo make install

The test suites that ship with the package can be invoked after the package has been installed by invoking the ‘installcheck’ target. This target can either be invoked as root, or as a normal user, like so:

     $> make installcheck

(Note: you must add the --enable-autotest flag to configure, above for the test suites to be invoked with ‘make installcheck’.)

The package can be cleanly removed by invoking the ‘uninstall’ target (as root):

     $> sudo make uninstall

Then the build directory and tarball can be simply removed:

     $> cd ..
     $> rm -rf build
     $> rm -rf netperf-2.3.7
     $> rm -f netperf-2.3.7.tar.bz2

Detailed Installation Instructions

More detailed installation instructions can be found in the Installation, contained in the distribution in ‘text’, ‘info’, ‘html’ and ‘pdf’ formats:

     $> cd ../netperf-2.3.7
     $> less doc/manual/netperf.txt
     $> lynx doc/manual/netperf.html
     $> info doc/manual/netperf.info
     $> xpdf doc/manual/netperf.pdf

The ‘text’ version of the manual is always available in the MANUAL file in the release.

The current manual is also always available online from The OpenSS7 Project website at:

     $> lynx http://www.openss7.org/netperf_manual.html

1 Introduction

This manual documents the design, implementation, installation, operation and future development schedule of the OpenSS7 NETPERF Utility package.

1.1 Overview

This manual documents the design, implementation, installation, operation and future development of the OpenSS7 NETPERF Utility package.

Netperf is a benchmark that can be used to measure various aspects of networking performance. Its primary focus is on bulk data transfer and request/response performance using SCTP, TCP or UDP, the X/Open XTI/TLI XNS 5.2 interface and the Berkeley Sockets interface. There are optional tests available to measure the performance of DLPI, Unix Domain sockets and STREAMS, the Fore ATM API and the HP HiPPI LLA interface.

This tool is maintained and informally supported by the IND Networking Performance Team. It is NOT supported via any of the normal Hewlett-Packard support channels. You are free to make enhancements and modifications to this tool.

1.2 Organization of this Manual

This manual is organized (loosely) into several sections as follows:

Introduction.	This introduction
Objective.	Objective of the package
Reference.	Contents of the package
Tests.	Tests included in the package
Conformance.	Conformance of the package
Releases.	Releases of the package
Installation.	Installation of the package
Troubleshooting.	Troubleshooting of the package

We thank you in advance for your comments, and hope that you find this tool useful.

The maintainers of netperf.

"How fast is it? It's so fast, that ..." ;-)

1.3 Conventions and Definitions

This manual uses texinfo typographic conventions.

You may not be familiar with some of the conventions and definitions used by this manual. Generally, items of particular importance, command line options, and commands will be in boldface type. Filenames and command line items requiring user substitution will appear in italicized type.

A sizespec is a one or two item list passed with a command line option that can set the value of one or two netperf parameters. If you wish to set both parameters to separate values, items should be separated by a comma, for example: "parm1, parm2". If you wish to set the first parameter without altering the value of the second, you should follow the first item with a comma, for example: "parm1,". Likewise, precede the item with a comma if you wish to set only the second parameter, for example ",parm2". An item without a comma will set both parameters. This last mode is the one most frequently used.

Netperf has two types of command line options. The first are global command line options. They are essentially any option that is not tied to a particular test, or group of tests. An example of a global command line option is the test type. The second options are test specific options. These are options that are only applicable to a particular test. An example of a test specific option would be the send socket buffer size for a TCP_STREAM test. Global command line options are specified first, test specific options second. They must be separated from each other by a "--" (two dashes). If you wish to give test specific options only, they must be preceded by "--".

For example:

     $ netperf -- -m 1024

2 Objective

3 Reference

3.1 Files

NETPERF installs the following utility programs in the system binary directory, /usr/sbin/:

sctp_stream_script
tcp_stream_script
udp_stream_script
sctp_rr_script
tcp_rr_script
udp_rr_script
sctp_range_script
tcp_range_script
snapshot_script
arr_script
packet_byte_script
netserver

NETPERF installs the following user programs in the user binary directory, /usr/bin/:

netperf
netperf_arr
netperf_packet_byte
netperf_sctp_range
netperf_sctp_rr
netperf_sctp_stream
netperf_snapshot
netperf_tcp_range
netperf_tcp_rr
netperf_tcp_stream
netperf_udp_range
netperf_udp_rr
netperf_udp_stream

NETPERF installs the following info files in the system info directory, /usr/share/info/:

netperf.info
netperf.info-1
netperf.info-2: These files contain this manual in GNU info format.

NETPERF installs the following manpage macros and reference database files in the system man directory, /usr/share/man/:⁶

netperf.macros: This file contains manual page macro definitions included by the manual pages included in the package.
netperf.refs: This file contains a reference database referenced by the manual pages included in the package.

NETPERF installs the following manual pages in the system man directory, /usr/share/man/man1/:

netperf.1
netperf_arr.1
netperf_packet_byte.1
netperf_sctp_range.1
netperf_sctp_rr.1
netperf_sctp_stream.1
netperf_snapshot.1
netperf_tcp_range.1
netperf_tcp_rr.1
netperf_tcp_stream.1
netperf_udp_range.1
netperf_udp_rr.1
netperf_udp_stream.1

NETPERF installs the following manual pages in the system man directory, /usr/share/man/man2/:

NETPERF installs the following manual pages in the system man directory, /usr/share/man/man3/:

NETPERF installs the following manual pages in the system man directory, /usr/share/man/man4/:

NETPERF installs the following manual pages in the system man directory, /usr/share/man/man5/:

netperf.5: manual page for the netperf(5) package.

NETPERF installs the following manual pages in the system man directory, /usr/share/man/man7/:

NETPERF installs the following manual pages in the system man directory, /usr/share/man/man8/:

sctp_range_script.8
sctp_rr_script.8
sctp_stream_script.8
tcp_range_script.8
tcp_rr_script.8
tcp_stream_script.8
udp_rr_script.8
udp_stream_script.8
snapshot_script.8
arr_script.8
packet_byte_script.8
netserver.8

3.2 Drivers

3.3 Modules

3.4 Libraries

3.5 Utilities

3.6 Development

4 Tests

4.1 Design

4.1.1 Design Basics

Netperf is designed around the basic client-server model. There are two executables – netperf and netserver. Generally you will only execute the netperf program – the netserver program will be invoked by the other system's inetd.

When you execute netperf, the first thing that happens is the establishment of a control connection to the remote system. This connection will be used to pass test configuration information and results to and from the remote system. Regardless of the type of test being run, the control connection will be a TCP connection using BSD sockets.

Once the control connection is up and the configuration information has been passed, a separate connection will be opened for the measurement itself using the APIs and protocols appropriate for the test. The test will be performed, and the results will be displayed.

Netperf places no traffic on the control connection while a test is in progress. Certain TCP options, such as SO_KEEPALIVE, if set as your system's default, may put packets out on the control connection.

4.1.2 CPU Utilization

CPU utilization is a frequently requested metric of networking performance. Unfortunately, it can also be one of the most difficult metrics to measure accurately. Netperf is designed to use one of several (perhaps platform dependent) CPU utilization measurement schemes. Depending on the CPU utilization measurement technique used, a unique single-letter code will be included in the CPU portion of the test banner for both the local and remote systems.

The default CPU measurement technique is based on the use of "loopers" which will sit in tight little loops consuming any CPU left over by the networking. This method is not without its added overhead, but wherever possible, card has been taken to keep that overhead to a minimum. If you would like to get an estimate of the overhead, run one test with CPU utilization, and one test without, and compare the throughputs. Use of loopers in measuring CPU utilization is indicated by the letter code "L".

NOTE: For accurate CPU utilization on MP systems, it is crucial that netperf and netserver know the number of processors on the system. For some systems (HP-UX) this can be determined programmatically. Other systems require the use of the "-n" global command line argument.

HP-UX 10.X offers a zero additional overhead, very accurate CPU utilization mechanism based on the pstat() system call. If you are compiling on HP-UX 10, you should replace the "-DUSE_LOOPER" in the makefile with "-DUSE_PSTAT" and recompile. When this method is being used, the letter code "T" will be displayed.

Other codes may be included in later versions of netperf. When the CPU utilization mechanism is unknown, either a "U" or a "?" will be displayed.

Great care should be exercised when looking at CPU utilization. Be certain you are familiar with the technique being used, and its implications. For example, a mechanism that is based solely on CPU charged to the netperf (netserver) process alone will likely under-report the real CPU utilization significantly. Much network processing takes place away from the user process context. Caveat Benchmarker!

4.1.3 Supported Interfaces

Sockets: BSD/POSIX Sockets Interface
XTI: X/Open Transport Interface (XTI/TLI) XNS 5.2 Interface
IPv6: BSD/POSIX IPv6 Sockets Interface
Unix: BSD/POSIX Unix Domain Sockets Interface
DLPI: X/Open XNS 5.2 Data Link Provider Interface (DLPI)
DNS: Directory Name Service

4.1.4 Supported Protocols

SCTP
TCP
UDP
UNIX
DL
DNS

4.1.5 Supported Tests

STREAM
MAERTS
SENDFILE
RR
NBRR
CRR
TRR
CC
DNS

4.2 Stream Tests

4.2.1 Available bulk data transfer performance tests

4.2.1.1 Forward Unidirectional Stream Performance Test (STREAM)

The intent of the STREAMS performance tests is to test forward unidirectional bulk data transfer in the direction from client to server. This is similar to the MAERTS tests, with the exception that the data transfer is in the forward direction. The basic test sequence is as follows:

     server: bind()
     server: listen()
     client: bind()
     client: connect()
     server: accept()
     client: send() [repeated]
     server: recv() [repeated]
     client: shutdown()
     client: close()
     server: close()
     test complete

There are three interface types that are of interest:

Stream

This is a connection-oriented reliable unidirectional bulk data transfer without regard for message boundaries. Protocols supporting this type of data transfer are SCTP, TCP, UNIX CO, and DLPI CO. Interfaces supporting this type of data transfer are Sockets, XTI, IPv6, UNIX and DLPI.

This interface type has been traditionally tested by netperf, however, connection-oriented tests have been lumped together with connectionless tests. Supported tests are:

SCTP_STREAM: SCTP BSD/POSIX IPv4 Sockets Interface (SOCK_STREAM)
TCP_STREAM: TCP BSD/POSIX IPv4 Sockets Interface (SOCK_STREAM)
SCTPIPV6_STREAM: SCTP BSD/POSIX IPv6 Sockets Interface (SOCK_STREAM)
TCPIPV6_STREAM: TCP BSD/POSIX IPv6 Sockets Interface (SOCK_STREAM)
STREAM_STREAM: Unix Domain BSD/POSIX Sockets Interface (SOCK_STREAM)
DLCO_STREAM: DLPI Connection-Oriented (DLCO)

Datagram

This is a connectionless unreliable unidirectional bulk data transfer regarding message boundaries. Protocols supporting this type of data transfer are UDP, UNIX CL and DLPI CL. Interfaces supporting this type of data transfer are Sockets, XTI, IPv6, UNIX and DLPI.

This interface type has been traditionally tested by netperf, however, connection-oriented tests have been lumped together with connectionless tests. Supported tests are:

UDP_STREAM
UDPIPV6_STREAM
DLCL_STREAM
FORE_STREAM

Packet

This is a connection-oriented reliable unidirectional bulk data transfer regarding message boundaries. Protocols supporting this type of data transfer are SCTP, and DLPI CO. Interfaces supporting this type of data transfer are Sockets, XTI, IPv6 and DLPI.

This interface type has not been traditionally tested by netperf; however, with the introduction of SCTP as a test protocol, these tests have been added to the netperf framework. Supported tests are:

SCTP_PACKET: SCTP BSD/POSIX IPv4 Sockets Interface (SOCK_SEQPACKET)
SCTPIPV6_PACKET: SCTP BSD/POSIX IPv6 Sockets Interface (SOCK_SEQPACKET)

4.2.1.2 Reverse Unidirectional Stream Performance Test (MAERTS)

The intent of the MAERTS performance tests is to test reverse unidirectional bulk data transfer in the direction from server to client. This is similar to the STREAM tests, with the exception that the data transfer is in the opposite direction. The basic test sequence is as follows:

     server: bind()
     server: listen()
     client: bind()
     client: connect()
     server: accept()
     server: send() [repeated]
     client: recv() [repeated]
     server: shutdown()
     server: close()
     client: close()
     test complete

Supported tests are:

SCTP_MAERTS: IPv4 SCTP BSD/POSIX Sockets Interface
TCP_MAERTS: IPv4 TCP BSD/POSIX Sockets Interface

4.2.1.3 Paged Unidirectional Stream Performance Test (SENDFILE)

The intent of the SENDFILE performance tests is to test paged unidirectional stream bulk data transfer in the direction from client to server. This is similar to the STREAM tests with the variation that the BSD-style sendfile() system call is used to transfer data directly from a mmap'ed file to the connection. The basic test sequence is as follows:

     server: bind()
     server: listen()
     client: bind()
     client: connect()
     server: accept()
     client: sendfile()
     server: recv() [repeated]
     client: shutdown()
     client: close()
     server: close()
     test complete

This test has traditionally only been available for TCP under netperf; however, OpenSS7 has added SCTP as another protocol for SENDFILE testing. These tests only used the BSD/POSIX IPv4 Sockets interface. Supported tests are:

SCTP_SENDFILE: IPv4 SCTP BSD/POSIX Sockets Interface
TCP_SENDFILE: IPv4 TCP BSD/POSIX Sockets Interface

4.2.2 Using Netperf to measure bulk data transfer performance

The most common use of netperf is measuring bulk data transfer performance. This is also referred to as "stream" or "unidirectional stream" performance. Essentially, these tests will measure how fast one system can send data to another and/or how fast the other system can receive it.

4.2.2.1 SCTP Stream Forward Performance

4.2.2.2 SCTP Stream Reverse Performance

4.2.2.3 SCTP Stream Sendfile Performance

4.2.2.4 TCP Stream Forward Performance

The TCP stream performance test is the default test for the netperf program. The simplest test is performed by entering the command:

     $ netperf -H remotehost

which will perform a 10 second test between the local system and the system identified by remotehost. The socket buffers on either end will be sized according to the systems' default and all TCP options (e.g. TCP_NODELAY) will be at their default settings.

To assist in measuring TCP stream performance, two script files are provided with the netperf distribution. They are tcp_stream_script and tcp_range_script. tcp_stream_script will invoke netperf based on the setting of script variables controlling socket and send sizes. tcp_range_script will perform a similar set of tests, with the difference being that where tcp_stream_script tests specific data points, tcp_range_script will perform tests at points within a specified range.

If you would like to perform tests other than those done by the scripts, you can invoke netperf manually. Some of the options you will likely want to experiment with are:

-s sizespec: which will set the local send and receive socket buffer sizes to the value(s) specified. [Default: system default socket buffer sizes]
-S sizespec: which behaves just like -s but for the remote system
-m value: set the local send size to value bytes. [Default: local socket buffer size]
-M value: which behaves like -m, setting the receive size for the remote system. [Default: remote receive socket buffer size]
-I value: set the test length to value seconds when value is > 0 and to |value| bytes when value < 0
-D: set the TCP_NODELAY option to true on both systems

This is not a complete list of options that can affect TCP stream performance, but it does cover those options that are used most often. A complete list of netperf options can be found in "Test Options".

4.2.2.5 TCP Stream Reverse Performance

4.2.2.6 TCP Stream Sendfile Performance

4.2.2.7 UDP Stream Performance

A UDP stream performance test is very similar to a TCP stream test. One difference is that the send size cannot be larger than the smaller of the local and remote socket buffer sizes. What this means is that you must make certain that when you specify the -m option, you use a value that is less than or equal to the socket buffer sizes (-s and -S). Also, since the UDP stream test is not the default test, the -t testname option must be specified, with the testname set to UDP_STREAM. So, a simple UDP stream test command might look something like this:

     $ netperf -H remotehost -t UDP_STREAM -- -m 1024

There is a script provided that performs various UDP stream performance tests. It is called udp_stream_script. As with TCP stream performance, you can use the script provided, or perform tests yourself to get data points not covered by the script.

NOTE: UDP is an unreliable protocol. It is important that you examine the results carefully as the reported send rate can be much higher than the actual receive rate. Great care should be taken when reporting UDP_STREAM test results to make sure they are not misleading. For example, one should always report both send and receive rates together for a UDP_STREAM test. If you are going to report a single number, you should report the receive rate.

NOTE: If you would like to "pace" the send rate of the UDP_STREAM test, add a "-DINTERVALS" to the makefile, do a ‘make clean’ and recompile. You can then use the -b and -w global options to set the burst size (sends) and wait time (milliseconds) respectively.

4.2.2.8 XTI SCTP Stream Performance

4.2.2.9 XTI TCP Stream Performance

The XTI TCP stream performance test is quite similar to the TCP_STREAM test. XTI requires a device file to be opened – as the device file is placed in different locations on different systems, it generally must be specified. The simplest XTI TCP stream test on HP-UX is performed by entering the command:

     $ netperf -H remotehost -t XTI_TCP_STREAM -- -X /dev/inet_cots

which will perform a 10 second test between the local system and the system identified by remotehost. The STREAMS buffers on either end will be sized according to the systems' default and all TCP options (e.g. T_TCP_NODELAY) will be at their default settings.

The test parameters for an XTI_TCP_STREAM test are the same as for a TCP_STREAM test with the addition of:

-X devspec: set the local/remote XTI device file name from devspec.

4.2.2.10 XTI UDP Performance

The XTI UDP stream performance test is quite similar to the UDP_STREAM test. XTI requires a device file be opened. As the device file is placed in different locations on different systems, it generally must be specified. The simplest XTI UDP stream test on HP-UX is performed by entering the command:

     $ netperf -H remotehost -t XTI_UDP_STREAM -- -X /dev/inet_clts

The test parameters for an XTI_UDP_STREAM test are the same as for a UDP_STREAM test with the addition of:

-X devspec: set the local/remote XTI device file name from devspec.

4.2.2.11 SCTP IPv6 Stream Forward Performance

4.2.2.12 TCP IPv6 Stream Forward Performance

4.2.2.13 UDP IPv6 Stream Forward Performance

4.2.2.14 DLPI Connection Oriented Stream Performance

NOTE: DLPI tests are not compiled-in by default with netperf. If you wish to measure performance over DLPI, you will need to add a -DDO_DLPI to the makefile and perhaps add to the "LIBS=" and recompile netperf and netserver.

A DLPI Connection Oriented Stream test (DLCO_STREAM) looks very similar to a TCP Stream test – they both use reliable, connection oriented protocols. The DLPI tests differs from the TCP test in that the message size must always be less than or equal to the local interface's MTU – DLPI does not provide TCP-style segmentation and reassembly.

The simplest DLPI Connection Oriented Stream test would look something like this:

     $ netperf -H remotehost -t DLCO_STREAM -- -m 1024

Here are some of the DLPI-specific command line options:

-D devspec: specify the local and/or remote DLPI device file name(s) (fully qualified). Syntax is the same as that of sizespec.
-m value: specify the send size, in bytes, for the local system. This must be less than or equal to the link MTU.
-M value: which behaves like -m, setting the receive size for the remote system.
-p ppaspec: set the local and/or remote DLPI PPA(s). Syntax is the same as that of a sizespec.
-r value: specify the request size, in bytes, for the test.
-R value: specify the response size, in bytes, for the test.
-s value: specify the 802.2 SAP for the test. This should not conflict with any assigned SAPs.
-w sizespec: specify the local send/recv window sizes in frames (where available).
-W sizespec: specify the remote sned/recv window sizes in frames (where available).

4.2.2.15 DLPI Connectionless Stream Performance

A DLPI Connectionless Stream test (DLCL_STREAM) is analogous to a UDP_STREAM test. They both make use of unreliable, connectionless transports. The DLPI test differs from the UDP test in that the message size must always be less than or equal to the link MTU – DLPI does not provide IP-like segmentation and reassembly functionality, and the netperf benchmark does not presume to provide one.

The simplest DLPI Connectionless Stream test command line would look something like this:

     $ netperf -H remotehost -t DLCL_STREAM -- -m 1024

Here are some of the DLPI-specific command line options for the DLCL_STREAM test:

-D devspec: specify the local and/or remote DLPI device file name(s) (fully qualified). Syntax is the same as that of sizespec.
-m value: specify the send size, in bytes, for the local system. This must be less than or equal to the link MTU.
-M value: which behaves like -m, setting the receive size for the remote system.
-p ppaspec: set the local and/or remote DLPI PPA(s). Syntax is the same as that of a sizespec.
-r value: specify the request size, in bytes, for the test.
-R value: specify the response size, in bytes, for the test.
-s value: specify the 802.2 SAP for the test. This should not conflict with any assigned SAPs.
-w sizespec: specify the local send/recv window sizes in frames (where available).
-W sizespec: specify the remote sned/recv window sizes in frames (where available).

4.2.2.16 Unix Domain Stream Sockets Performance

NOTE: Unix Domain Socket tests are not compiled into netperf by default. If you wish to measure the performance of Unix Domain Sockets, you must recompile netperf and netserver with -DDO_UNIX added to the makefile.

A Unix Domain Stream Socket Stream test (STREAM_STREAM) is very much like a TCP_STREAM test.

The simplest Unix Domain Socket Stream test command line would look something like this:

     $ netperf -t STREAM_STREAM

The -H global command line option is not valid for Unix Domain Socket test and should not be specified.

Here are some of the Unix Domain-specific command line options for the STREAM_STREAM test:

-m value: set the local send size to value bytes. [Default: local socket buffer size]
-M value: which behaves like -m, setting the receive size for the remote system. [Default: remote receive socket buffer size]
-p dirspec: set the directory where pipes will be created. [Default:system default for the tempnam() call]
-s sizespec: which will set the local send an receive socket buffer sizes to the value(s) specified. [Default: system default socket buffer sizes]
-S sizespec: which behaves just like -s but for the remote system.

4.2.2.17 Unix Domain Datagram Sockets Performance

A Unix Domain Datagram Socket stream test (DG_STREAM) is very much like a TCP_STREAM test except that message boundaries are preserved. The simplest Unix Domain Datagram Socket stream test command line would look something like this:

     $ netperf -t DG_STREAM

The -H global command line option is not valid for a Unix Domain Socket test and should not be specified. Here are some of the test specific command line options available in a DG_STREAM test.

-m value: set the local send size to value bytes. [Default: local socket buffer size]
-M value: which behaves like -m, setting the receive size for the remote system. [Default: remote receive socket buffer size]
-p dirspec: set the directory where pipes will be created. [Default:system default for the tempnam() call]
-s sizespec: which will set the local send an receive socket buffer sizes to the value(s) specified. [Default: system default socket buffer sizes]
-S sizespec: which behaves just like -s but for the remote system.

4.2.2.18 Fore ATM API Stream Performance

NOTE: Fore ATM API tests are not compiled into netperf by default. If you wish to measure the performance of connections over the Fore ATM API, you must recompile netperf and netserver with -DDO_FORE added to the makefile.

A Fore ATM API stream test (FORE_STREAM) is very much like a UDP_STREAM test.

NOTE: The Fore ATM API explores an unreliable protocol. It is important that you examine the results carefully as the reported send rate can be much higher than the actual receive rate. Great care should be taken when reporting FORE_STREAM test results to make sure they are not misleading. For example, one should always report both send and receive rates together for a FORE_STREAM test. If you are going to report a single number, you should report the receive rate.

The simplest Fore ATM API stream test command line would look something like this:

     $ netperf -t FORE_STREAM -H remotehost

Here are some of the test specific command line options applicable to a FORE_STREAM test.

-a AAL: use the ATM Adaptation Layer number AAL to encapsulate packets. Specifying 3 or 4 will yield AAL3/4, and 5 will yield AAL5. [Default: 5 -> AAL5]
-b sizespec: set the mean burst target and/or minimum in units of kilobit packets. The first value is target and the second is minimum. [Default: 0,0]
-d devspec: set the name of the ATM device file to be opened. [Default: /dev/atm]
-m value: set the local send size to value bytes. This must not be larger than the ATM MTU. [Default: ATM MTU]
-M value: which behaves like -m, setting the receive size for the remote system. [Default: ATM MTU]
-p sizespec: set the peak bandwidth target and/or minimum in units of kilobits/s. The first value is target and the second is minimum. [Default: 0,0 -> network assigned]
-P sizespec: set the mean bandwidth target and/or minimum in units of kilobits/s. The first value is target and the second is minimum. [Default: 0,0 -> network assigned]

4.3 Request/Response Tests

4.3.1 Available request/response performance tests

4.3.1.1 Request/Response Performance Test (RR)

4.3.1.2 Non-Blocking Request/Response Performance Test (NBRR)

4.3.1.3 Connect/Request/Response Performance Test (CRR)

4.3.1.4 Transaction Request/Response Performance Test (TRR)

4.3.1.5 Connect/Close Performance Test (CC)

4.3.2 Using Netperf to measure request/response performance

Request/response performance is the second test that can be investigated with netperf. Generally speaking, netperf request/response performance is quoted as "transactions/s" for a given request and response size. A transaction is defined as the exchange of a single request and a single response. From a transaction rate, one can infer one way and route-trip average latency.

4.3.2.1 SCTP Request/Response Performance

4.3.2.2 SCTP Non-Blocking Request/Response Performance

4.3.2.3 SCTP Request/Response Connect Performance

4.3.2.4 SCTP Request/Response Transaction Performance

4.3.2.5 SCTP Connect/Close Performance

4.3.2.6 TCP Request/Response Performance

The TCP request/response test can be invoked with netperf through the use of the -t option with an argument of TCP_RR. So, a "default" request/response command would look something like this:

     $ netperf -H remotehost -t TCP_RR

and will use the system default socket buffer sizes, a default request size of 1 byte, and a default response size of 1 byte.

As with the stream performance tests, a script is available to assist you in generating TCP request/response performance numbers. It is called tcp_rr_script. However, if you should need to generate numbers at point of your own choosing, these command line options will be of use:

-r sizespec: set the request and/or response sizes based on sizespec.
-I value: set the test duration based on value. For value > 0, test duration will be value seconds. Otherwise, test duration will be |value| transactions.
-s sizespec: which will set the local send and receive socket buffer sizes to the value(s) specified. [Default: system default socket buffer sizes]
-S sizespec: which behaves like -s but for the remote system
-D: set the TCP_NODELAY option to true on both systems

The request and response sizes will be buffer sizes posted to send and receive. The -m and -M options are not meaningful for a TCP_RR test. As TCP is a stream protocol and not a message protocol, it is necessary to loop on receives until the entire message is delivered. The buffer pointer passed to the first receive for an individual transaction will be aligned and offset as requested by the user. It will be incremented by the number of bytes received each time until the entire request/response is received. The buffer pointer will be realigned and offset for the next transaction.

4.3.2.7 TCP Non-Blocking Request/Response Performance

TCP_NBRR is the same as TCP_RR except that it uses POSIX non-blocking sockets.

4.3.2.8 TCP Request/Response Connect Performance

The TCP_CRR test is a test which mimics the http protocol used by most web servers. Instead of simply measuring the performance of request/response in the same connection, it establishes a new connection for each request/response pair. The test-specific parameters are the same as the TCP_RR test with one addition:

-p max[,min]: set the minimum or maximum port numbers used by the client side.

It is important that this test run for a reasonable length of time – at least two minutes. This is related to the behaviour of various TCP implementations. If you run the test for shorter periods of time, the results could be higher than seen in a steady-state condition. So, a good TCP_CRR command line to simulate a web-server might look like:

     $ netperf -t TCP_CRR -I 120 -H remotehost -- -r 32,1024

4.3.2.9 TCP Request/Response Transaction Performance

4.3.2.10 TCP Connect/Close Performance

4.3.2.11 UDP Request/Response Performance

UDP request/response performance works just like TCP request/response performance. All the options available for TCP are available for UDP with the exception of the -D option: TCP_NODELAY has no meaning for a UDP test. To invoke a UDP request/response test, use an argument of UDP_RR with the -t option to produce the a command something like this:

     $ netperf -H remotehost -t UDP_RR

Again, a script is provided which will generate results for some of the more common data points. It is named udp_rr_scrip.

4.3.2.12 XTI SCTP Request/Response Performance

4.3.2.13 XTI TCP Request/Response Performance

The XTI TCP request/response test can be invoked with netperf through the use of the -t option with an argument of XTI_TCP_RR. Not all systems put the requisite device files in the same location, so, a "default" request/response command on HP-UX would look something like this:

     $ netperf -H remotehost -t XTI_TCP_RR -- -X /dev/inet_cots

and will use the system default socket buffer sizes, a default request size of 1 byte, and a default response size of 1 byte.

The command line options for the XTI_TCP_RR test are the same as the TCP_RR test, with the following additions:

-X devspec: set the local/remote XTI device file name from devspec.

The request and response sizes will be the buffer sizes posted to send and receive. As TCP is a stream protocol and not a message protocol, it is necessary to loop on receives until the entire message is delivered. The buffer pointer passed to the first receive for an individual transaction will be aligned and offset as requested by the user. It will be incremented by the number of bytes received each time until the entire request/response is received. The buffer pointer will be realigned and offset for the next transaction.

4.3.2.14 XTI UDP Request/Response Performance

The XTI UDP requset/response test can be invoked with netperf through the use of the -t option with an argument of XTI_UDP_RR. Not all systems put the requisite device files in the same location, so, a "default" request/response command on HP-UX would look something like this:

     $ netperf -H remotehost -t XTI_UDP_RR -- -X /dev/inet_clts

and will use the system default socket buffer sizes, a default request size of 1 byte, and a default response size of 1 byte.

The command line options for the XTI_UDP_RR test are the same as the UDP_RR test, with the following additions:

-X devspec: set the local/remote XTI device file name from devspec.

The request and response sizes will be the buffer sizes posted to send and receive.

4.3.2.15 SCTP IPv6 Request/Response Performance

4.3.2.16 TCP IPv6 Request/Response Performance

4.3.2.17 UDP IPv6 Request/Response Performance

4.3.2.18 DLPI Connection Oriented Request/Response Performance

4.3.2.19 DLPI Connectionless Request/Response Performance

4.3.2.20 Unix Domain Stream Socket Request/Response Performance

4.3.2.21 Unix Domain Datagram Socket Request/Response Performance

4.3.2.22 Unix Domain Stream Socket Request/Response Light-Weight Process Performance

4.3.2.23 Unix Domain Datagram Socket Request/Response Light-Weight Process Performance

4.3.2.24 Fore ATM API Request/Response Performance

4.4 Global Options

4.5 Test Options

5 Conformance

6 Releases

This is the OpenSS7 Release of the OpenSS7 NETPERF Utility package, modified for use with OpenSS7 Stream Control Transmission Protocol (SCTP) Linux Native Kernel and Linux Fast-STREAMS or Linux STREAMS⁷ SVR 4.2 STREAMS releases.

The purpose of providing a separate release of this package was to provide support for SCTP as well as providing the ability to use GNU autoconf tools for maintenance and binary RPM release of the package; also, to separate the OpenSS7 NETPERF Utility tools, headers, drivers and modules from the Linux STREAMS⁸ package for use with both Linux STREAMS⁹ and Linux Fast-STREAMS in preparation for replacement of the former by the later.

The following sections provide information on OpenSS7 NETPERF Utility releases as well as compatibility information of OpenSS7 release to the original HP releases of the OpenSS7 NETPERF Utility package, as well as Linux kernel compatibility.

6.1 Prerequisites

The quickest and easiest way to ensure that all prerequisites are met is to download and install this package from within the OpenSS7 Master Package, openss7-0.9.2.G, instead of separately.

Prerequisites for the OpenSS7 NETPERF Utility package are as follows:

	− A fairly LSB compliant GNU/Linux distribution.¹⁰
	− Linux 2.4 kernel (2.4.10 - 2.4.27), or
	− Linux 2.6 kernel (2.6.3 - 2.6.26);
	− glibc2 or better.
	− GNU groff (for man pages).¹¹
	− GNU texinfo (for info files).

(Note: If you acquired netperf a part of the OpenSS7 Master Package, then the dependencies listed below will already have been met by unpacking the master package.)

OpenSS7 Linux Fast-STREAMS, streams-0.9.2.4. ¹²
OpenSS7 STREAMS Compatibility Modules, strcompat-0.9.2.7.
OpenSS7 STREAMS XNS, strxns-0.9.2.7.
OpenSS7 STREAMS XTI/TLI, strxnet-0.9.2.12.
OpenSS7 STREAM Network Services Library, strnsl-0.9.2.4. (Optional.)
OpenSS7 STREAMS INET, strinet-0.9.2.7.
OpenSS7 STREAMS SCTP, strsctp-0.9.2.9.
OpenSS7 STREAMS Channels, strchan-0.9.2.4.
OpenSS7 STREAMS X.25, strx25-0.9.2.1.
OpenSS7 STREAMS ISO, striso-0.9.2.4.
OpenSS7 STREAMS ISDN, strisdn-0.9.2.4.
OpenSS7 STREAMS SS7, strss7-0.9a.8.
OpenSS7 STREAMS SIGTRAN, sigtran-0.9.2.4.
OpenSS7 STREAMS VoIP, strvoip-0.9.2.4.

If you need to rebuild the package from sources with modifications, you will need a larger GNU tool chain as described in See Downloading from CVS.

6.2 Compatibility

This section discusses compatibility with major prerequisites.

6.2.1 GNU/Linux Distributions

OpenSS7 NETPERF Utility is compatible with the following Linux distributions:¹³

CentOS Enterprise Linux 3.4 (centos34) TBD
CentOS Enterprise Linux 4.0 (centos4) TBD
CentOS Enterprise Linux 4.92 (centos49) TBD
CentOS Enterprise Linux 5.0 (centos5)
CentOS Enterprise Linux 5.1 (centos51)
CentOS Enterprise Linux 5.2 (centos52)
Debian 3.0r2 Woody (deb3.0) TBD
Debian 3.1r0a Sarge (deb3.1) TBD
Debian 4.0r1 Etch (deb4.0)
Debian 4.0r2 Etch (deb4.0)
Debian 4.0r3 Etch (deb4.0)
Fedora Core 1 (FC1) TBD
Fedora Core 2 (FC2) TBD
Fedora Core 3 (FC3) TBD
Fedora Core 4 (FC4) TBD
Fedora Core 5 (FC5) TBD
Fedora Core 6 (FC6) TBD
Fedora 7 (FC7)
Fedora 8 (FC8)
Fedora 9 (FC9)
Gentoo 2006.1 (untested) TBD
Gentoo 2007.1 (untested) TBD
Lineox 4.026 (LEL4) TBD
Lineox 4.053 (LEL4) TBD
Mandrakelinux 9.2 (MDK92) TBD
Mandrakelinux 10.0 (MDK100) TBD
Mandrakelinux 10.1 (MDK101) TBD
Mandriva Linux LE2005 (MDK102) TBD
Mandriva Linux LE2006 (MDK103) TBD
Mandriva One (untested)
RedHat Linux 7.2 (RH7)
RedHat Linux 7.3 (RH7)
RedHat Linux 8.0 (RH8) TBD
RedHat Linux 9 (RH9) TBD
RedHat Enterprise Linux 3.0 (EL3) TBD
RedHat Enterprise Linux 4 (EL4)
RedHat Enterprise Linux 5 (EL5)
SuSE 8.0 Professional (SuSE8.0) TBD
SuSE 9.1 Personal (SuSE9.1) TBD
SuSE 9.2 Professional (SuSE9.2) TBD
SuSE OpenSuSE (SuSEOSS) TBD
SuSE 10.0 (SuSE10.0) TBD
SuSE 10.1 (SuSE10.1) TBD
SuSE 10.2 (SuSE10.2) TBD
SuSE 10.3 (SuSE10.3) TBD
SuSE 11.0 (SuSE11.0)
SLES 9 (SLES9) TBD
SLES 9 SP2 (SLES9) TBD
SLES 9 SP3 (SLES9) TBD
SLES 10 (SLES10)
Ubuntu 5.10 (ubu5.10) TBD
Ubuntu 6.03 LTS (ubu6.03) TBD
Ubuntu 6.10 (ubu6.10) TBD
Ubuntu 7.04 (ubu7.04) TBD
Ubuntu 7.10 (ubu7.10)
Ubuntu 8.04 (ubu8.04)
WhiteBox Enterprise Linux 3.0 (WBEL3) TBD
WhiteBox Enterprise Linux 4 (WBEL4) TBD

When installing from the tarball (see Installing the Tar Ball), this distribution is probably compatible with a much broader array of distributions than those listed above. These are the distributions against which the current maintainer creates and tests builds.

6.2.2 Kernel

The OpenSS7 NETPERF Utility package compiles as a Linux kernel module. It is not necessary to patch the Linux kernel to build or use the package.¹⁴ Nor do you have to recompile your kernel to build or use the package. OpenSS7 packages use autoconf scripts to adapt the package source to your existing kernel. The package builds and runs nicely against production kernels from the distributions listed above. Rather than relying on kernel versions, the autoconf scripts interrogate the kernel for specific features and variants to better adapt to distribution production kernels that have had patches applied over the official kernel.org sources.

The OpenSS7 NETPERF Utility package is compatible with 2.4 kernel series after 2.4.10 and has been tested up to and including 2.4.27. It has been tested from 2.6.3 up to and including 2.6.26 (with Fedora 9, openSUSE 11.0 and Ubuntu 8.04 patchsets). Please note that your mileage may vary if you use a kernel more recent than 2.6.26.4: it is difficult to anticipate changes that kernel developers will make in the future. Many kernels in the 2.6 series now vary widely by release version and if you encounter problems, try a kernel within the supported series.

UP validation testing for kernels is performed on all supported architectures. SMP validation testing was initially performed on UP machines, as well as on an Intel 3.0GHz Pentium IV 630 with HyperThreading enabled (2x). Because HyperThreading is not as independent as multiple CPUs, SMP validation testing was limited. Current releases have been tested on dual 1.8GHz Xeon HP servers (2x) as well as dual quad-core SunFire (8x) servers.

It should be noted that, while the packages will configure, build and install against XEN kernels, that problems running validation test suites against XEN kernels has been reported. XEN kernels are explicitly not supported. This may change at some point in the future if someone really requires running OpenSS7 under a XEN kernel.

6.2.3 Architectures

The OpenSS7 NETPERF Utility package compiles and installs on a wide range of architectures. Although it is believed that the package will work on all architectures supported by the Linux kernel being used, validation testing has only been performed with the following architectures:

ix86
x86_64
ppc (MPC 860)
ppc64

32-bit compatibility validation testing is performed on all 64-bit architectures supporting 32-bit compatibility. If you would like to validate an OpenSS7 package on a specific machine architecture, you are welcome to sponsor the project with a test machine.

6.2.4 Linux STREAMS

The OpenSS7 NETPERF Utility package is currently compatible with Linux STREAMS,¹⁵ however, to use the OpenSS7 NETPERF Utility package with LiS requires use of the OpenSS7 release packages of LiS. The OpenSS7 NETPERF Utility package is compatible with the OpenSS7 LiS-2.18.7 release that is available from the The OpenSS7 Project Downloads Page. But, do not use LiS: it is buggy, unsupported and deprecated. Use Linux Fast-STREAMS instead.

6.2.5 Linux Fast-STREAMS

The OpenSS7 NETPERF Utility package is currently compatible with Linux Fast-STREAMS (LfS). The OpenSS7 NETPERF Utility package is compatible with the OpenSS7 streams-0.9.2.4 release that is available from the The OpenSS7 Project Downloads Page.

6.2.6 HP Netperf

This section addresses compatibility issues between OpenSS7 and Hewlett-Packard releases of netperf.

netperf-2.3.7 and Netserver Compatibility

OpenSS7 modifications to support SCTP does not alter the data structures or exchange between the netperf client and the netserver server. New structures and test definitions have been added for SCTP that are largely consistent with those of TCP. Specifically, a netperf-2.3 client should be able to connect and perform tests with a netperf-2.3.7 server. Also, a netperf-2.3.7 client should be able to connect and perform tests (other than SCTP) with a netperf-2.3 server.

netperf-2.3.7 and Option Compatibility

OpenSS7 releases provide all options compiled-in to the client and server. This obviates the need for editing makefiles and recompiling the client or server from source as is described in the Hewlett-Packard Company documentation.

netperf-2.3.7 and SCTP Compatibility

SCTP Socket API tests are (likely) only compatible with the OpenSS7 Sockets implementations of SCTP. The reason for this is that the OpenSS7 Sockets implementations use the POSIX standard socket API rather than the non-standard socket API described in documents such as draft-stewart-tsvwg-sctpsocket-xx.txt.

SCTP XTI API tests are (likely) only compatible with the OpenSS7 STREAMS implementation of SCTP, and the OpenSS7 XTI over Sockets implementation (see Introduction) with the OpenSS7 Linux Native SCTP Sockets implementation. The reason for this is that the OpenSS7 STREAMS implementation uses the X/Open XNS 5.2 SUSv2 UNIX'98 standard XTI interface rather than the non-standard socket API described in documents such as draft-stewart-tsvwg-sctpsocket-xx.txt.

6.3 Release Notes

The sections that follow provide information on OpenSS7 releases of the OpenSS7 NETPERF Utility package as well as compatibility information of OpenSS7 releases to the original Hewlett-Packard Company releases.

Major changes for release netperf-2.3.7

This is the seventh full release of the OpenSS7 NETPERF Utility package.

This release is largely a maintenance release that provides support for more distributions an architectures as well as tracking feature updates on related packages.

Major features since the last public release are as follows:

Minor documentation corrections.
License upgrade to AGPL Version 3.
Support for flex 2.5.33 in maintainer mode.
Ability to strap out major documentation build and installation primarily for embedded targets.
Improvements to common build process for embedded and cross-compile targets.
Updated tool chain to m4-1.4.12, autoconf-2.63 and texinfo-4.13.
Conversion of RPM spec files to common approach for major subpackages.
Updated references database for manual pages and roff documents.
Build system now builds yum(8) repositories for RPMs and apt-get(8) repositories for DEBs. Installation documentation has been updated to include details of repository install sourcesref.
Added MODULE_VERSION to all modules and drivers.
Fixed long_options termination error.
Added -I option to SCTP tests to permit the addresses to bind to for both the local netperf client and remote netserver server. This permits addresses to be excluded from the bind for testing in single-homed and limited multi-homed configurations.
Updated documentation for the bind feature.

This is a public stable production grade release of the package: it deprecates previous releases. Please upgrade to the current release before reporting bugs.

As with other OpenSS7 releases, this release configures, compiles, installs and builds RPMs and DEBs for a wide range of Linux 2.4 and 2.6 RPM- and DPKG-based distributions, and can be used on production kernels without patching or recompiling the kernel.

This package is publicly released under the GNU Affero General Public License Version 3 as well as the HP license (see LICENSE in the distribution for more information.) The release is available as an autoconf tarball, SRPM, DSC, and set of binary RPMs and DEBs. See the downloads page for the autoconf tarballs, SRPMs and DSCs. For tarballs, SRPMs, DSCs and binary RPMs and DEBs, see the netperf package page.

See http://www.openss7.org/codefiles/netperf-2.3.7/ChangeLog and http://www.openss7.org/codefiles/netperf-2.3.7/NEWS in the release for more information. Also, see the netperf.pdf manual in the release (also in html http://www.openss7.org/netperf_manual.html).

For the news release, see http://www.openss7.org/rel20081029_7.html.

Major changes for release netperf-2.3.6

This is the sixth full release of the OpenSS7 NETPERF Utility package.

This release is largely a maintenance release that provides support for more distributions an architectures as well as tracking feature updates on related packages.

Major features since the last public release are as follows:

Support build on openSUSE 10.2.
Support build on Fedora 7 with 2.6.21 kernel.
Support build on CentOS 5.0 (RHEL5).
Support build on Ubuntu 7.04.
Updated to gettext 0.16.1.
Supports build on Fedora Core 6.
Support for recent distributions and tool chains.

Major changes for release netperf-2.3.5

This is the fifth full release of the OpenSS7 NETPERF Utility package.

This release is largely a maintenance release that provides support for more distributions an architectures as well as tracking feature updates on related packages.

Major features since the last public release are as follows:

Support for autoconf 2.61, automake 1.10 and gettext 0.16.
Support for Ubuntu 6.10 distribution and bug fixes for i386 kernels.
The package now looks for other subpackages with a version number as unpacked by separate tarball.

Major changes for release netperf-2.3.4

This is the fourth full release of the OpenSS7 NETPERF Utility package.

This release is largely a maintenance release that provides support for more distributions an architectures as well as tracking feature updates on related packages:

Updates to permit use with strinet-0.9.2.7 second generation UDP driver, strsctp-0.9.2.9 STREAMS SCTP driver, sctp-0.2.27 Sockets SCTP driver.
Added send-pr scripts for automatic problem report generation. (Please do not report bugs on LiS.)
Added --disable-devel configure option to suppress building and installing development environment. This feature is for embedded or pure runtime targets that do not need the development environment (static libraries, manual pages, documentation).
Improved compiler flag generation and optimizations for recent gcc compilers and some idiosyncratic behaviour for some distributions (primarily SUSE). Optimized compilation is now available also for user level programs in addition to kernel programs. Added new --with-optimize option to configure to accomplish this.
Better detection of SUSE distributions, release numbers and SLES distributions: support for additional SuSE distributions on ix86 as well as x86_64. Added distribution support includes SLES 9, SLES 9 SP2, SLES 9 SP3, SLES 10, SuSE 10.1.
Many documentation updates for all OpenSS7 packages. Automated release file generation making for vastly improved and timely text documentation present in the release directory.
Now builds 32-bit compatibility libraries and tests them against 64-bit kernel modules and drivers. The ‘make installcheck’ target will now automatically test both 64-bit native and 32-bit compatibility versions, one after the other, on 64-bit platforms.
Includes results of performance testing of the new second generation UDP driver (implemented completely in STREAMS instead of using an internal socket).
Includes workup of benchmark scripts for SCTP, TCP and UDP. Added a scls_show option to perform ‘scls -c’ (see scls(1)) to show STREAMS module and driver statistics between test sample points when verbosity is set to 2 and XTI is being used. This assists with performance testing as it shows the counts accumulated to put and service routine throughout the Stream. It was used in UDP2 testing of the strinet package and will come in handy for the SCTP testing.

Major changes for release netperf-2.3.4.rc3

Third release candidate. This is a maintenance release candidate. This release candidate includes:

Automated release file generation making for vastly improved and timely text documentation present in the release directory.
Many documentation updates (for all OpenSS7 packages).
Includes the changes made to the strsctp drivers at the 2006 SCTP Interop at the University of British Columbia. This version was interoperability tested with all implementations present.
Provides support for additional SuSE distributions on ix86 as well as x86_64. Added distribution support includes SLES 9, SLES 9 SP2, SLES 9 SP3, SLES 10, SuSE 10.1.
Includes workup of benchmark scripts for SCTP, TCP and UDP. Added a scls_show option to perform ‘scls -c’ (see scls(1)) to show STREAMS module and driver statistics between test sample points when verbosity is set to 2 and XTI is being used. This assists with performance testing as it shows the counts accumulated to put and service routine throughout the Stream. It was used in UDP2 testing of the strinet package and will come in handy for the SCTP testing.

This was an internal alpha test release candidate and was not released publicly. This release was only available to subscribers to and sponsors of the OpenSS7 Project.

Major changes for release netperf-2.3.4.rc2

Second release candidate. This is a maintenance release candidate. This release candidate includes:

Includes results of performance testing of the new second generation UDP driver (implemented completely in STREAMS instead of using an internal socket).
Includes support for SuSE 10.1.

This was an internal alpha test release candidate and was not released publicly. This release was only available to subscribers to and sponsors of the OpenSS7 Project.

Major changes for release netperf-2.3.4rc1

First release candidate for Mark Fugate. This is a maintenance release candidate. This release candidate includes:

Added --enable-devel configure option for embedded targets.
Added send-pr script for automatic problem report generation.

This was an internal alpha test release candidate and was not released publicly. This release was only available to subscribers to and sponsors of the OpenSS7 Project.

Major changes for release netperf-2.3.3

This release is primarily to support additional compilers (gcc 4.0.2), architectures (x86_64, SMP, 32-bit compatibility), recent Linux distributions (EL4, SuSE 10, LE2006, OpenSuSE) and kernels (2.6.15).

Corrections for and testing of 64-bit clean compile and test runs on x86_64 architecture. Some bug corrections resulting from gcc 4.0.2 compiler warnings.

Major changes for release netperf-2.3.2

Many corrections (but not enough) are included to use the package for XTI INET testing. UDP works now, but TCP is not completely corrected yet (and, therefore, neither is SCTP). These capabilities could not have possibly worked in the original netperf-2.3 release. The next release should have TCP and SCTP corrected for XTI.

Corrections included to make the package cross-build for NexusWare as well as recent 2.6.14 (FC4) kernels.

What remains to be done is to merge in the latest upstream release of netperf into this package and contribute XTI corrections back upstream.

Initial release netperf-2.3.1

Initial autoconf/RPM packaging of the netperf release. It is based on the Hewlett-Packard Company netperf-2.3 release.

This release provides modifications to support the Stream Control Transmission Protocol (SCTP) and provides tests for the Sockets API for the OpenSS7 Linux Native Kernel version of SCTP as well as tests for the XTI API for the OpenSS7 STREAMS version of SCTP. In addition, use of the XTI API for TCP and UDP tests is supported using the OpenSS7 STREAMS INET package.

SCTP Sockets API tests depend upon the availability of an the OpenSS7 Sockets implementation of SCTP in an OpenSS7 patched kernel. Some binary kernels and prepatched kernel source for popular architectures are provided as RPMs from the OpenSS7 Project download page.

SCTP XTI API tests depend upon the availability of the OpenSS7 STREAMS implementation of SCTP. Some binary and source packages for LiS STREAMS, Linux Fast-STREAMS, the strxnet XTI/TLI library and the strsctp package are available from the OpenSS7 Project download page. Introduction.

Under Linux, the TCP and UDP XTI API tests depend upon the availability of the OpenSS7 INET driver. Some binary and source packages for LiS STREAMS, Linux Fast-STREAMS, the strxnet XTI/TLI library and the strinet package (see Introduction) are available from the OpenSS7 Project download page. Introduction.

This release also provides updates to the antiquated netperf-2.1 release documentation distributed with netperf-2.3.

6.4 Maturity

The OpenSS7 Project adheres to the following release philosophy:

pre-alpha release
alpha release
beta release
gamma release
production release
unstable release

6.4.1 Pre-Alpha Releases

Pre-alpha releases are releases that have received no testing whatsoever. Code in the release is not even known to configure or compile. The purpose of a pre-alpha release is to make code and documentation available for inspection only, and to solicit comments on the design approach or other characteristics of the software package.

Pre-alpha release packages ship containing warnings recommending that the user not even execute the contained code.

6.4.2 Alpha Releases

Alpha releases are releases that have received little to no testing, or that have been tested and contains known bugs or defects that make the package unsuitable even for testing. The purpose for an alpha release are the same as for the pre-alpha release, with the additional purpose that it is an early release of partially functional code that has problems that an external developer might be willing to fix themselves and contribute back to the project.

Alpha release packages ship containing warnings that executing the code can crash machines and might possibly do damage to systems upon which it is executed.

6.4.3 Beta Releases

Beta releases are releases that have received some testing, but the testing to date is not exhaustive. Beta release packages do not ship with known defects. All known defects are resolved before distribution; however, as exhaustive testing has not been performed, unknown defects may exist. The purpose for a beta release is to provide a baseline for other organizations to participate in the rigorous testing of the package.

Beta release packages ship containing warnings that the package has not been exhaustively tested and that the package may cause systems to crash. Suitability of software in this category for production use is not advised by the project; however, as always, is at the discretion of the user of the software.

6.4.4 Gamma Releases

Gamma releases are releases that have received exhaustive testing within the project, but external testing has been minimal. Gamma release packages do not ship with known defects. As exhaustive internal testing has been performed, unknown defects should be few. Please remember that there is NO WARRANTY on public release packages.

Gamma release packages typically resolve problems in previous beta releases, and might not have had full regression testing performed. Suitability of software in this category for production use is at the discretion of the user of the software. The OpenSS7 Project recommends that the complete validation test suites provided with the package be performed and pass on target systems before considering production use.

6.4.5 Production Releases

Production releases are releases that have received exhaustive testing within the project and validated on specific distributions and architectures. Production release packages do not ship with known defects. Please remember that there is NO WARRANTY on public release packages.

Production packages ship containing a list of validated distributions and architectures. Full regression testing of any maintenance changes is performed. Suitability of software in this category for production use on the specified target distributions and architectures is at the discretion of the user. It should not be necessary to preform validation tests on the set of supported target systems before considering production use.

6.4.6 Unstable Releases

Unstable releases are releases that have received extensive testing within the project and validated on a a wide range of distributions and architectures; however, is has tested unstable and found to be suffering from critical problems and issues that cannot be resolved. Maintenance of the package has proved impossible. Unstable release packages ship with known defects (and loud warnings). Suitability of software in this category for production use is at the discretion of the user of the software. The OpenSS7 Project recommends that the problems and issues be closely examined before this software is used even in a non-production environment. Each failing test scenario should be completely avoided by the application. OpenSS7 beta software is more stable that software in this category.

6.5 Bugs

6.5.1 Defect Notices

OpenSS7 NETPERF Utility could contain unknown defects. This is a beta release. Some defects could be harmful. Validation testing has been performed by the OpenSS7 Project on this software for only a restricted set of systems. The software might fail to configure or compile on other systems. The OpenSS7 Project recommends that you do not use this software for purposes other than validation testing and evaluation, and then only with care. Use at your own risk. Remember that there is NO WARRANTY.¹⁶

This software is beta software. As such, it might crash your kernel. Installation of the software might mangle your header files or Linux distribution in such a way as to make it unusable. Crashes could lock your system and rebooting the system might not repair the problem. You can possibly lose all the data on your system. Because this software might crash your kernel, the resulting unstable system could possibly destroy computer hardware or peripherals making them unusable. You might void the warranty on any system on which you run this software. YOU HAVE BEEN WARNED.

6.5.2 Known Defects

With the exception of packages not originally created by the OpenSS7 Project, the OpenSS7 Project software does not ship with known bugs in any release stage except pre-alpha. OpenSS7 NETPERF Utility had no known bugs at the time of release.

Nevertheless, the OpenSS7 Project does not validate the OpenSS7 NETPERF Utility package, but simply uses it for benchmark performance testing. Following are some of the expected difficulties with the package that have not yet been discovered:

The use of XTI Streams was incorrect in most places. Originally the package used socket system calls on Streams (which of course fails on TPI Streams). Some corrections have been made to allow the package to function properly with UDP under XTI using the strxnet and strinet packages. It is expected that there will be similar problems for TCP, SCTP, TI, DLPI and other Streams.
No bug fixes from the original Netperf development stream have been rolled back into this release. Therefore, any bugs reported on the regular Netperf release package probably still exist unfixed in this release package.

6.5.3 Defect History

This section contains historical bugs that were encountered during development and their resolutions. This list serves two purposes:

It captures bugs encountered between releases during development that could possibly reoccur (and the Moon is made of blue cheese). It therefore provides a place for users to look if they encounter a problem.
It provides a low overhead bug list between releases for developers to use as a TODO list.

Bugs

001. 2007-07-21T20:50:14-0600: It was discovered that the long_options arrays were not zero terminated causing the netperf program to segfault when issued a non-existent option.
*fixed* in netperf-2.3.7.

6.6 Schedule

Things to do:

Merge in upstream changes from the latest Hewlett-Packard release of the Netperf package into the OpenSS7 Modified version. I would really like to do this but don't have the time for it right now. If someone is willing to dive in and give this a try, send me the patches.
Netperf is capable of performing performance testing on lksctp as well. I would like to modify the OpenSS7 version of Netperf to support both so that performance comparison testing can be done between lkstcp (which sucks of course) and OpenSS7 Linux Natve Sockets version.
Get the OpenSS7 NETPERF Utility version working also with OpenSS7 Linux Native Sockets SCTP in addition to the current STREAMS SCTP XTI support. This would not only allow Netperf to be used successfully with OpenSS7 Linux Native SCTP, but it would also comparison tests between STREAMS and Sockets versions. This is something that I would really like to do. As Linux Fast-STREAMS STREAMS-based pipes beat FC4 Native pipes on 2.6.14 in a performance test, it would be interesting to see whether the STREAMS version can out perform the Sockets version. This would be an answer to the time old question as to whether Sockets or STREAMS is faster.

Redo performance tests for strxnet/strinet package using recent release of OpenSS7 NETPERF Utility.
*done*
Perform x86_64 HT SMP testing.
*done*

6.7 History

For the latest developments with regard to history of changes, please see the ChangeLog file in the release package.

7 Installation

7.1 Repositories

The OpenSS7 NETPERF Utility package release can be accessed from the repositories of The OpenSS7 Project. For rpm(1) based systems, the package is available in a yum(8) repository based on repomd XML and may also be accessed using zypper(8) or yast(8). For dpkg(1) based systems, the package is available in a apt(8) repository.

By far the easiest (most repeatable and manageable) form for installing and using OpenSS7 packages is to install packages from the yum(8) or apt(8) repositories. If your distribution does not support yum(8), zypper(8), yast(8) or apt(8), then it is still possible to install the RPMs or DEBs from the repositories using rpm(1), dpkg(1); or by using wget(1) and then installing them from RPM or DEB using rpm(1) or dpkg(1) locally.

If binaries are not available for your distribution or specific kernel, but your distribution supports rpm(1) or dpkg(1), the next best method for installing and using OpenSS7 packages is to download and rebuild the source RPMs or DSCs from the repository. This can also be performed with yum(8), zypper(8), yast(8), apt(8); or directly using wget(1), rpm(1) or dpkg(1).

If your architecture does not support rpm(1) or dpkg(1) at all, or you have special needs (such as cross-compiling for embedded targets), the final resort method is to download, configure, build and install from tarball. In this later case, the easiest way to build and install OpenSS7 packages from tarball is to use the tarball for the OpenSS7 Master Package, openss7-0.9.2.G.

7.1.1 Repositories for YUM

To install or upgrade from the OpenSS7 repomd repositories, you will need a file in your /etc/yum.repo.d/ directory. This file can be obtained directly from the OpenSS7 repository, like so:

     $> REPOS="http://www.openss7.org/repos/rpms"
     $> wget $REPOS/centos/5.2/x86_64/repodata/openss7.repo
     $> sudo cp -f openss7.repo /etc/yum.repo.d/
     $> sudo yum makecache

This example assumes the the distribution is ‘centos’ and the distribution release is ‘5.2’ and the architecture requires is ‘x86_64’. Another example would be $REPOS/i686/suse/11.0/i686/repodata/openss7.repo, for using yum(8) with SUSE.

Once the repository is set up, OpenSS7 includes a number of virtual package definitions that eas the installation and removal of kernel modules, libraries and utilities. Downloading, configuring, building and installation for a single-kernel distribution is as easy as:

     $> sudo yum install netperf

Removing the package is as easy as:

     $> sudo yum remove netperf

If you have difficulty downloading the openss7.repo file, edit the following information into the file and place it into the /etc/yum.repo.d/openss7.repo file:

     -| [openss7]
     -| enabled = 1
     -| name = OpenSS7 Repository
     -| baseurl = http://www.openss7.org/repos/rpms/centos/5.2/x86_64
     -| gpgcheck = 1
     -| gpgkey = http://www.openss7.org/pubkey.asc

Note that it is also possible to point to these repositories as an additional installation source when installing CentOS, RedHat, Fedora, or others. You will have an additional STREAMS category from which to choose installation packages.

Some additional installation real or virtual package names and the installations they accomplish are as follows:

‘netperf’: This package can be used to install or remove the entire OpenSS7 NETPERF Utility package. When installing, kernel modules will be installed automatically for the highest version kernel on your system. When removing, all corresponding kernel modules will also be removed.
‘netperf-devel’: This package can be used to install or remove the development components of the OpenSS7 NETPERF Utility package. When installing, ‘netperf’ and appropriate kernel module and kernel module development and debug packages will also be installed. When removing, the development package and all kernel module development and debug packages will also be removed.

For assistance with specific RPMs, see Downloading the Binary RPM.

7.1.2 Repositories for APT

For assistance with specific DEBs, see Downloading the Debian DEB.

7.2 Downloading

The OpenSS7 NETPERF Utility package releases can be downloaded from the downloads page of The OpenSS7 Project. The package is available as a binary RPM (for popular architectures) a source RPM, Debian binary DEB and source DSC, or as a tar ball. If you are using a browsable viewer, you can obtain the OpenSS7 release of netperf from the links in the sections that follow.

By far the easiest (most repeatable and manageable) form for installing and using OpenSS7 packages is to download and install individual packages from binary RPM or DEB. If binary RPMs or DEBs are not available for your distribution, but your distribution supports rpm(1) or dpkg(1), the next best method for installing and using OpenSS7 packages is to download and rebuild the source RPMs or DSCs.

7.2.1 Downloading with YUM

OpenSS7 repositories support yum(8) and zypper(8) in repomd XML format as well as YaST and YaST2 formats.

OpenSS7 includes virtual packages that ease the installation and removal of kernel modules, libraries and utilities. Downloading, configuration, building and installation for a signle-kernel distribution installation is as easy as:

     % sudo yum install netperf

This and additional packages for installation are detailed as follows:

netperf

Install this package if you need the runtime netperf package.

          % sudo yum install netperf

This will install the netperf, netperf-lib and netperf-KVERSION RPMs, where ‘KVERSION’ is the highest version number kernel on your system.

Remove this package if you need to remove all vestages of the netperf package.

          % sudo yum remove netperf

This will remove the netperf, netperf-lib, netperf-devel, netperf-KVERSION and netperf-devel-KVERSION RPMs for all kernels on your system.

netperf-devel

Install this package if you need the development netperf package.

          % sudo yum install netperf-devel

This will install the netperf, netperf-lib, netperf-devel, netperf-KVERSION and netperf-devel-KVERSION RPMs, where ‘KVERSION’ is the highest version number kernel on your system.

Remove this package if you do not need development capabilities for the netperf package for any kernel.

          % sudo yum remove netperf-devel

This will remove the netperf-devel and netperf-devel-KVERSION RPMs for all kernels on your system.

netperf-lib

This package is an auxillary package that should be removed and inserted automatically by yum(8). In rare instances you might need to remove or install this package explicitly.

7.2.2 Downloading with APT

OpenSS7 repositries support apt(8) repositorie digests and signatures.

7.2.3 Downloading the Binary RPM

To install from binary RPM, you will need several of the RPM for a complete installation. Binary RPM fall into several categories. To download and install a complete package requires the appropriate RPM from each of the several categories below, as applicable. Some release packages do not provide RPMs in each of the several categories.

To install from Binary RPM, you will need all of the following independent packages for your architecture.

Independent RPM

Independent RPM are not dependent on the STREAMS package. For example, the source package ‘netperf-source-2.3.7-1.7.2.noarch.rpm’, is not dependent on kernel nor STREAMS package.

All of the following STREAMS independent RPM are required for your architecture. Binary RPMs listed here are for example only: additional binary RPMs are available from the downloads site. If your architecture is not available, you can build binary RPM from the source RPM (see see Building from the Source RPM).

Architecture Independent

netperf-dev-2.3.7-1.7.2.noarch.rpm: The netperf-dev package contains the device definitions necessary to run applications programs developed for OpenSS7 NETPERF Utility.¹⁷
netperf-doc-2.3.7-1.7.2.noarch.rpm: The netperf-doc package contains this manual in plain text, postscript, pdf and html forms, along with the meta-information from the netperf package. It also contains all of the manual pages necessary for developing OpenSS7 NETPERF Utility applications and OpenSS7 NETPERF Utility STREAMS modules or drivers.
netperf-init-2.3.7-1.7.2.noarch.rpm: The netperf-init package contains the init scripts and provides the ‘postinst’ scripts necessary to create kernel module preloads and modules definitions for all kernel module ‘core’ subpackages.
netperf-source-2.3.7-1.7.2.noarch.rpm: The netperf-source package contains the source code necessary for building the OpenSS7 NETPERF Utility release. It includes the autoconf(1) configuration utilities necessary to create and distribute tarballs, rpm and deb/dsc. ¹⁸

Architecture Dependent

The following Architecture Dependent packages are required for your architecture. If your architecture is not on the list, you can build binary RPM from the source RPM (see see Building from the Source RPM).

netperf-devel-2.3.7-1.7.2.i686.rpm: The netperf-devel package contains library archives for static compilation, header files to develop OpenSS7 NETPERF Utility modules and drivers. This also includes the header files and static libraries required to compile OpenSS7 NETPERF Utility applications programs.
netperf-lib-2.3.7-1.7.2.i686.rpm: The netperf-lib package contains the run-time shared libraries necessary to run application programs and utilities developed for the netperf package. ¹⁹

STREAMS-Dependent RPM

STREAMS-Dependent RPM are dependent upon the specific STREAMS package being used, either Linux STREAMS or Linux Fast-STREAMS. Packages dependent upon Linux STREAMS will have LiS in the package name. Packages dependent upon Linux Fast-STREAMS will have streams in the package name. Note that some STREAMS-Dependent RPM are also Kernel-Dependent RPM as described below.

One of the following STREAMS-Dependent packages is required for your architecture. If your architecture is not on the list, you can build binary RPM from the source RPM (see see Building from the Source RPM).

netperf-LiS-2.3.7-1.7.2.i686.rpm: The netperf-LiS package contains the netserver(8) and netperf(1) programs compiled to work with OpenSS7 Kernel and LiS STREAMS release of the INET driver and SCTP.
netperf-streams-2.3.7-1.7.2.i686.rpm: The netperf-streams package contains the netserver(8) and netperf(1) programs compiled to work with OpenSS7 Kernel and Linux Fast-STREAMS release of the INET driver and SCTP.
netperf-LiS-util-2.3.7-1.7.2.i686.rpm: The netperf-LiS-util package provides administrative and configuration test utilities and commands associated with the OpenSS7 NETPERF Utility package. Because this package must link a STREAMS-specific library, it is a STREAMS-Dependent package. Use the netperf-LiS-util package if you have LiS installed.
netperf-streams-util-2.3.7-1.7.2.i686.rpm: The netperf-streams-util package provides administrative and configuration test utilities and commands associated with the OpenSS7 NETPERF Utility package. Because this package must link a STREAMS-specific library, it is a STREAMS-Dependent package. Use the netperf-streams-util package if you have streams installed.

Dependent RPM

To be able to perform the SCTP and XTI tests supported by the release, it may be necessary to download and install some of the following packages to satisfy dependencies:

LiS-core-2.18.7-1.i686.rpm: This package provides one of the two SVR 4.2 STREAMS facilities for use by netperf-2.3.7. This (or the other) STREAMS package is required to support the DLPI and XTI tests. Since the netperf binary is directly linked with the libLiS.so.0.0.0 library for support of the getpmsg(2) and putpmsg(2) system calls, this package is tightly tied to the DLPI tests. This package is required by netperf-LiS-2.3.7-1.7.2.i686.rpm. Other subpackages created by LiS-2.18.7-1.src.rpm may be necessary to by able to recompile netperf-2.3.7.
streams-core-0.9.2.4-1.i686.rpm: This package provides the other of the two SVR 4.2 STREAMS facilities for use by netperf-openss7-2.3.7. This (or the other) STREAMS package is required to support the DLPI and XTI tests. Since the netperf-openss7 binary is directly linked with the libstreams.so.0.0.0 library for support of the getpmsg(2) and putpmsg(2) system calls, this package is tightly tied to the DLPI tests. This package is required by netperf-openss7-streams-2.3.7-1.i686.rpm. Other subpackages created by streams-0.9.2.4-1.src.rpm may be necessary to by able to recompile netperf-openss7-2.3.7.
strxns-core-0.9.2.7-1.i686.rpm: This package provides the DLPI implementation for Linux Ethernet devices required by the netperf-openss7-2.3.7 DLPI tests. Other subpackages created by strxns-0.9.2.7-1.src.rpm may be necessary to by able to recompile netperf-openss7-2.3.7.
strxnet-core-0.9.2.12-1.i686.rpm: This package provides the X/Open XNS 5.2 XTI/TLI library (libxnet) necessary to support the XTI tests. Other subpackages created by strxnet-0.9.2.12-1.src.rpm may be necessary to by able to recompile netperf-openss7-2.3.7. Introduction.
strinet-core-0.9.2.7-1.i686.rpm: This package provides the XTI interface to the Linux Socket SCTP, TCP and UDP implementations in support of XTI SCTP, XTI TCP and XTI UDP tests. This package is only required if it is desired to run XTI SCTP, XTI TCP or XTI UDP tests on Linux using the strinet driver. Introduction. The strinet driver is an XTIoS (XTI over Sockets) implementation that provides a STREAMS XTI interface to the native Linux Kernel socket code. Other subpackages created by strinet-0.9.2.7-1.src.rpm may be necessary to by able to recompile netperf-openss7-2.3.7.
strsctp-core-0.9.2.9-1.i686.rpm: This package provides the XTI interface to the Linux STREAMS implementation of SCTP in support of XTI SCTP tests. This package is only required if it is desired to run XTI SCTP tests on Linux. This is a native STREAMS implementation of the Stream Control Transmission Protocol (SCTP) that does not use XTIoS. Other subpackages created by strsctp-0.9.2.9-1.src.rpm may be necessary to by able to recompile netperf-openss7-2.3.7.

Configuration and Installation

To configure, build and install the binary RPM, See Configuring the Binary RPM.

7.2.4 Downloading the Debian DEB

To install from binary DEB, you will need several of the DEB for a complete installation. Binary DEB fall into several categories. To download and install a complete package requires the appropriate DEB from each of the several categories below, as applicable. Some release packages do not provide DEBs in each of the several categories.

To install from Binary DEB, you will need all of the following independent packages for your architecture.

Independent DEB

Independent DEB are dependent on neither the Linux kernel version, nor the STREAMS package. For example, the source package ‘netperf-source_2.3.7-0_i386.deb’, is not dependent on kernel nor STREAMS package.

All of the following STREAMS independent DEB are required for your architecture. Binary DEBs listed here are for example only: additional binary DEBs are available from the downloads site. If your architecture is not available, you can build binary DEB from the Debian DSC (see see Building from the Debian DSC).

Architecture Independent

netperf-dev_2.3.7-0_all.deb: The netperf-dev package contains the device definitions necessary to run applications programs developed for OpenSS7 NETPERF Utility. ²⁰
netperf-doc_2.3.7-0_all.deb: The netperf-doc package contains this manual in plain text, postscript, pdf and html forms, along with the meta-information from the netperf package. It also contains all of the manual pages necessary for developing OpenSS7 NETPERF Utility applications and OpenSS7 NETPERF Utility STREAMS modules or drivers.
netperf-init_2.3.7-0_all.deb: The netperf-init package contains the init scripts and provides the postinst scripts necessary to create kernel module preloads and modules definitions for all kernel module ‘core’ subpackages.
netperf-source_2.3.7-0_all.deb: The netperf-source package contains the source code necessary for building the OpenSS7 NETPERF Utility release. It includes the autoconf(1) configuration utilities necessary to create and distribute tarballs, rpms and deb/dscs. ²¹

Architecture Dependent

The following Architecture Dependent packages are required for your architecture. If your architecture is not on the list, you can build binary DEB from the Debian DSC (see see Building from the Debian DSC).

netperf-devel_2.3.7-0_i386.deb: The netperf-devel package contains library archives for static compilation, header files to develop OpenSS7 NETPERF Utility modules and drivers. This also includes the header files and static libraries required to compile OpenSS7 NETPERF Utility applications programs.
netperf-lib_2.3.7-0_i386.deb: The netperf-lib package contains the run-time shared libraries necessary to run application programs and utilities developed for the netperf package. ²²

STREAMS-Dependent DEB

STREAMS-Dependent DEB are dependent upon the specific STREAMS package being used, either Linux STREAMS or Linux Fast-STREAMS. Packages dependent upon Linux STREAMS will have LiS in the package name. Packages dependent upon Linux Fast-STREAMS will have streams in the package name. Note that some STREAMS-Dependent DEB are also Kernel-Dependent DEB as described below.

One of the following STREAMS-Dependent packages is required for your architecture. If your architecture is not on the list, you can build binary DEB from the Debian DSC (see see Building from the Debian DSC).

netperf-LiS-util_2.3.7-0_i386.deb: The netperf-LiS-util package provides administrative and configuration test utilities and commands associated with the OpenSS7 NETPERF Utility package. Because this package must link a STREAMS-specific library, it is a STREAMS-Dependent package. Use the netperf-LiS-util package if you have LiS installed.
netperf-streams-util_2.3.7-0_i386.deb: The netperf-streams-util package provides administrative and configuration test utilities and commands associated with the OpenSS7 NETPERF Utility package. Because this package must link a STREAMS-specific library, it is a STREAMS-Dependent package. Use the netperf-streams-util package if you have streams installed.

Configuration and Installation

To configure, build and install the Debian DEB, See Configuring the Debian DEB.

7.2.5 Downloading the Source RPM

If you cannot obtain a binary RPM for your architecture, or would like to roll you own binary RPM, download the following source RPM.

netperf-2.3.7-1.src.rpm: This is the source RPM for the package. From this source RPM it is possible to build binary RPM for any supported architecture and for any 2.4 or 2.6 kernel, for either Linux STREAMS or Linux Fast-STREAMS.

Configuration

To configure the source RPM, See Configuring the Source RPM.

7.2.6 Downloading the Debian DSC

If you cannot obtain a binary DEB for your architecture, or would like to roll your own DEB, download the following Debian DSC.

netperf_2.3.7-0.dsc
netperf_2.3.7-0.tar.gz: This is the Debian DSC for the package. From this Debian DSC it is possible to build binary DEB for any supported architecture and for any 2.4 or 2.6 kernel, for either Linux STREAMS or Linux Fast-STREAMS.

Configuration

To configure the source RPM, See Configuring the Debian DSC.

7.2.7 Downloading the Tar Ball

For non-rpm(1) and non-dpkg(1) architectures, download the tarball as follows:

netperf-2.3.7.tar.gz
netperf-2.3.7.tar.bz2: These are the tar(1) balls for the release. These tar(1) balls contain the autoconf(1) distribution which includes all the source necessary for building and installing the package. These tarballs will even build Source RPM and Binary RPM on rpm(1) architectures and Debian DSC and DEB on dpkg(1) architectures.

The tar ball may be downloaded easily with wget(1) as follows:

     % wget http://www.openss7.org/netperf-2.3.7.tar.bz2

     % wget http://www.openss7.org/netperf-2.3.7.tar.gz

Note that you will need an OpenSS7 Project user name and password to download release candidates (which are only available to subscribers and sponsors of the OpenSS7 Project).

Unpacking the Archive

After downloading one of the tar balls, unpack the archive using one of the following commands:

     % wget http://www.openss7.org/netperf-2.3.7.tar.gz
     % tar -xzvf netperf-2.3.7.tar.gz

     % wget http://www.openss7.org/netperf-2.3.7.tar.bz2
     % tar -xjvf netperf-2.3.7.tar.bz2

Either will create a subdirectory name netperf-2.3.7 containing all of the files and subdirectories for the netperf package.

Configuration

To configure and install the tar ball, See Configuring the Tar Ball.

7.2.8 Downloading from CVS

If you are a subscriber or sponsor of The OpenSS7 Project with CVS archive access privileges then you can download release, mid-release or release candidate versions of the netperf package from the project CVS archive.

The OpenSS7 NETPERF Utility package is located in the netperf module of /var/cvs. For release tag information, see Releases.

To access the archive from the project CVS pserver, use the following commands to check out a version from the archive:

     % export CVSROOT='-d:pserver:username@cvs.openss7.com:2401/var/cvs'
     % cvs login
     Password: *********
     % cvs co -r netperf_2.3.7 netperf
     % cvs logout

It is, of course, possible to check out by date or by other criteria. For more information, see cvs(1).

Preparing the CVS Working Directory

Although public releases of the netperf package do not require reconfiguration, creating a configurable directory from the CVS archive requires tools not normally distributed with the other releases.

The build host requires the following GNU tools:

m4 1.4.12
autoconf 2.63
automake 1.10.1
libtool 2.2.4
gettext 0.17
flex 2.5.33
bison 2.3

Most desktop development GNU/Linux distributions wil have these tools; however, some non-development or server-style installations might not and they must be installed separately.²³

Also, these tools can be acquired from the FSF website in the free software directory, and also at the following locations:

It should be stressed that, in particular, the autoconf(1), and automake(1), must be at version releases 2.63 and 1.10.1. The versions normally distributed in some mainstream GNU/Linux distributions are, in fact, much older than these versions.²⁴ GNU version of these packages configured and installed to default directories will install in /usr/local/ allowing them to coexist with distribution installed versions.

For building documentation, the build host also requires the following documentation tools:

gs 6.51 or ghostscript 6.51, or newer.
tetex 3.0 or texlive 2007, or newer.
texinfo 4.13a or newer.
transfig 3.2.3d or newer.
imagemagick 5.3.8 or ImageMagick 5.3.8, or newer.
groff 1.17.2 or newer.
gnuplot 3.7 or newer.
latex2html 1.62 or newer.

Most desktop GNU/Linux distributions will have these tools; however, some server-style installations (e.g. Ubuntu-server, SLES 9 or Fedora 6 or 7) will not and they must be installed separately.²⁵

Note that texinfo 4.12 must not be used as it breaks the build process.

For uncooked manual pages, the entire groff(1) package is required on Debian and Ubuntu systems (the base package does not include grefer(1) which is used extensively by uncooked manual pages). The following will get what you need:

     Debian: % apt-get install groff_ext
     Ubuntu: % apt-get install groff

In addition, the build host requires a complete tool chain for compiling for the target host, including kernel tools such as genksyms(8) and others.

If you wish to package rpms on an rpm(1) system, or debs on a dpkg(1) system, you will need the appropriate tool chain. Systems based on rpm(1) typically have the necessary tool chain available, however, dpkg(1) systems do not. The following on a Debian or Ubuntu system will get what you need:

     % apt-get install debhelper
     % apt-get install fakeroot

To generate a configuration script and the necessary scriptlets required by the GNU autoconf(1) system, execute the following commands on the working directory:

     % autoreconf -fiv netperf

where, netperf is the name of the directory to where the working copy was checked out under the previous step. This command generates the configure script and other missing pieces that are normally distributed with the release Tar Balls, SRPMs and DSCs.

Make sure that ‘autoreconf --version’ returns ‘2.63’. Otherwise, you may need to perform something like the following:

     % PATH="/usr/local/bin:$PATH"
     % autoreconf -fiv netperf

After reconfiguring the directory, the package can then be configured and built using the same instructions as are used for the Tar Ball, see Configuring the Tar Ball, and Building from the Tar Ball.

Do note, however, that make(1) will rebuild the documentation that is normally released with the package. Additional tools may be necessary for building the documentation. To avoid building and installing the documentation, use the --disable-devel or --disable-docs option to configure described in Configuring the Tar Ball.

When configuring the package in a working directory and while working a change-compile-test cycle that involves configuration macros or documentation, I find it of great advantage to invoke the GNU configure options --enable-maintainer-mode, --enable-dependency-tracking and --disable-devel. The first of these three options will add maintainer-specific targets to any generated Makefile, the second option will invoke automatic dependency tracking within the Makefile so rebuilds after changes to macro, source or documentation files will be automatically rebuilt; and the last option will suppress rebuilding and reinstalling documentation manual pages and header files. Header files will still be available under the /usr/src directory.

7.3 Configuration

7.3.1 Configuring the Binary RPM

In general the binary RPM do not require any configuration, however, during installation it is possible to relocate some of the installation directories. This allows some degree of customization. Relocations that are available on the binary RPM are as follows:

netperf-dev-2.3.7-1.7.2.i686.rpm

(not relocatable)

netperf-devel-2.3.7-1.7.2.i686.rpm

/usr/lib: This relocatable directory contains netperf libraries.
/usr/include/netperf: This relocatable directory contains netperf header files.

netperf-doc-2.3.7-1.7.2.i686.rpm

/usr/share/doc: This relocatable directory contains all package specific documentation (including this manual). The subdirectory in this directory is the netperf-2.3.7 directory.
/usr/share/info: This relocatable directory contains info files (including the info version of this manual).
/usr/share/man: This relocatable directory contains manual pages.

netperf-LiS-lib-2.3.7-1.7.2.i686.rpm

netperf-streams-lib-2.3.7-1.7.2.i686.rpm

/usr/lib: This relocatable directory contains the run-time shared libraries necessary to run applications programs and utilities developed for OpenSS7 NETPERF Utility.
/usr/share/locale: This relocatable directory contains the locale information for shared library files.

netperf-source-2.3.7-1.7.2.i686.rpm

/usr/src: This relocatable directory contains the source code.

netperf-LiS-util-2.3.7-1.7.2.i686.rpm

netperf-streams-util-2.3.7-1.7.2.i686.rpm

/usr/bin: This relocatable directory contains binary programs and utilities.
/usr/sbin: This relocatable directory contains system binary programs and utilities.
/usr/libexec: This relocatable directory contains test programs.
/etc: This relocatable directory contains init scripts and configuration information.

Installation

To install the binary RPM, See Installing the Binary RPM.

7.3.2 Configuring the Debian DEB

In general the binary DEB do not require any configuration.

Installation

To install the Debian DEB, See Installing the Debian DEB.

7.3.3 Configuring the Source RPM

When building from the source RPM (see Building from the Source RPM), the rebuild process uses a number of macros from the user's .rpmmacros file as described in rpm(8).

Following is an example of the ~/.rpmmacros file that I use for rebuilding RPMS:

     #
     # RPM macros for building rpms
     #
     
     %vendor OpenSS7 Corporation
     %distribution OpenSS7
     %disturl http://www.openss7.org/
     %packager Brian Bidulock <bidulock@openss7.org>
     %url http://www.openss7.org/
     
     %_signature gpg
     %_gpg_path /home/brian/.gnupg
     %_gpg_name openss7@openss7.org
     %_gpgbin /usr/bin/gpg
     
     %_source_payload w9.bzdio
     %_binary_payload w9.bzdio
     
     %_unpackaged_files_terminate_build 1
     %_missing_doc_files_terminate_build 1
     %_use_internal_dependency_generator 0
     %_repackage_all_erasures 0
     %_rollback_transaction_on_failure 0
     
     %configure2_5x %configure
     %make make

When building from the source RPM (see Building from the Source RPM), it is possible to pass a number of additional configuration options to the rpmbuild(1) process.

The additional configuration options are described below.

Note that distributions that use older versions of rpm do not have the --with or --without options defined. To achieve the same effect as:

     --with someparm=somearg

do:

     --define "_with_someparm --with-someparm=somearg"

This is a generic description of common rpmbuild(1) options. Not all rpmbuild(1) options are applicable to all SRPMs. Options that are kernel module specific are only applicable to SRPMs that build kernel modules. STREAMS options are only applicable to SRPMs that provide or require STREAMS.

--define "_kversion $PACKAGE_KVERSION": Specifies the kernel version other than the running kernel for which to build. If _kversion is not defined when rebuilding, the environment variable PACKAGE_KVERSION is used. If the environment variable PACKAGE_KVERSION is not defined, then the version of the running kernel (i.e. discovered with ‘uname -r’) is used as the target version for kernel-dependent packages. This option can also be defined in an .rpmspec file using the macro name ‘_kversion’.
--with checks
--without checks: Enable or disable preinstall checks. Each packages supports a number of preinstall checks that can be performed by invoking the ‘check’ target with automake(1). These currently consist of checking each kernel module for unresolved kernel symbols, checking for documentation for exported kernel module symbols, checking for documentation for exported library symbols, checking for standard options for build and installable programs, checking for documentation for built and installable programs. Normally these checks are only run in maintainer mode, but can be enabled and disabled with this option.
--with k-optimize=HOW
--without k-optimize: Specify ‘HOW’ optimization, normal, size, speed or quick. size compiles kernel modules -Os, speed compiles kernel modules -O3, and quick compiles kernel modules -O0. The default is normal. Use with care.
--with cooked-manpages
--without cooked-manpages: Some systems do not like grefer(1) references in manual pages.²⁶ This option will cook soelim(1), refer(1), tbl(1) and pic(1) commands from the manual pages and also strip groff(1) comments. The default is to leave manual pages uncooked: they are actually smaller that way.
--with public
--without public: Release public packages or private packages. This option has no effect on the netperf package. The default is to release public packages.
--with k-debug
--without k-debug: Specifies whether kernel debugging is to be performed on the build kernel modules. Mutually exclusive with test and safe below. This has the effect of removing static and inline attributes from functions and invoking all debugging macros in the code. The default is to not perform kernel debugging.
--with k-test
--without k-test: Specifies whether kernel testing is to be performed. Mutually exclusive with debug above and safe below. This has the effect of removing static and inline attributes from functions and invoking most debugging macros in the code. The default is to not perform kernel testing.
--with k-safe
--without k-safe: Specifies whether kernel saftey is to be performed. Mutually exclusive with debug and test above. This has the effect of invoking some more pedantic assertion macros in the code. The default is not to apply kernel safety.
--with k-inline
--without k-inline: Specifies whether kernel inline functions are to be placed inline. This has the effect of adding the -finline-functions flag to CFLAGS for compiling kernel modules. Linux 2.4 kernels are normally compiled -O2 which does not respect the inline directive. This compiles kernel modules with -finline-functions to get closer to -O3 optimization. For better optimization controls, See Configuring the Tar Ball.
--with k-modversions
--without k-modversions: Specifies whether kernel symbol versions are to be applied to symbols exported by package kernel modules. The default is to version exported module symbols. This package does not export symbols so this option has no effect.
--with devfs
--without devfs: Specifies whether the build is for a device file system daemon enabled system with autoloading, or not. The default is to build for devfsd(1) autoloading when CONFIG_DEVFS_FS is defined in the target kernel. The ‘rebuild’ target uses this option to signal to the RPM spec file that the ‘dev’ subpackage need not be built. This option does not appear when the package has no devices.
--with devel
--without devel: Specifies whether to build development environment packages such as those that include header files, static libraries, manual pages and texinfo(1) documentation. The default is to build development environment packages. This option can be useful when building for an embedded target where only the runtime components are desired.
--with docs
--without docs: Specifies whether to build and install major documentation such manual pages and texinfo(1) documentation. The default is to build and install documentation. This option can be useful when building for an embedded target where only the runtime and static compile components are desired, but not major documentation. This option does not override the setting of --without devel.
--with tools
--without tools: Specifies whether user space packages are to be built. The default is to build user space packages. This option can be useful when rebuilding for multiple architectures and target kernels. The ‘rebuild’ automake(1) target uses this feature when rebuilding for all available architectures and kernels, to rebuild user packages once per architecture instead of once per kernel.
--with modules
--without modules: Specifies whether kernel modules packages are to be built. The default is to build kernel module packages. This option can be useful when rebuilding for multiple architectures and target kernels. The ‘rebuild’ automake(1) target uses this feature to rebuild for all available architectures and kernels.
--with lis
--without lis: Specifies that the package is to be rebuilt against Linux STREAMS. The default is to automatically identify whether LiS or streams is loaded on the build system and build accordingly.
--with lfs
--without lfs: Specifies that the package is to be rebuilt against Linux Fast-STREAMS. The default is to automatically identify whether LiS or streams is loaded on the build system and build accordingly.

In addition, the following rpm options, specific to the OpenSS7 NETPERF Utility package are available:

--without netperf-dirty: Disable code that dirties buffers before calls to send. This option defaults to ‘enabled’.
--without netperf-histogram: Disable code to keep a histogram of request-response times or time spend in send(). This option defaults to ‘enabled’.
--with netperf-old-histogram: Enable old pre-2.2pl6 formatted histogram. This option defaults to ‘disabled’.
--without netperf-intervals: Disable code to allow pacing of sends in UDP, TCP or SCTP tests. This may have unexpected results on non-HPUX systems. This option defaults to ‘enabled’.
--without netperf-do-dlpi: Disable code to test to the DLPI implementation. This option defaults to ‘enabled’.
--without netperf-do-sctp: Disable code to test the SCTP implementation. This option defaults to ‘enabled’.
--without netperf-do-select: Disable code to do select() on receive. This option defaults to ‘enabled’.
--with netperf-do-lwp: This option defaults to ‘disabled’.
--without netperf-do-nbrr: Disable code to do non-blocking request-response. This option defaults to ‘enabled’.
--without netperf-do-xti: Disable code to test the XTI implementation. This option defaults to ‘enabled’.
--without netperf-do-xti-sctp: Disable code to test the XTI SCTP implementation. This option defaults to ‘enabled’.
--without netperf-do-unix: Disable code to test the UNIX domain implementation. This option defaults to ‘enabled’.
--without netperf-do-1644: Disable code to test T/TCP vs TCP transactions. This option defaults to ‘enabled’.
--without netperf-do-first-burst: Disable code to create an initial burst. This option defaults to ‘enabled’.
--with netperf-use-looper: Enable looper or soaker processes. When enabled, use looper or soaker processes to measure CPU utilization. These will be forked-off at the beginning. If you are running this way, it is important to see how much impact these have on the measurement. A loop back test on uniprocessor should be able to consume approximately 100% of the CPU, and the difference between throughput with USE_LOOPER_CPU and without should be small for a real network. If it is not, then some work probably needs to be done on reducing the priority of the looper processes. This option defaults to ‘disabled’. Do not enable this option for Linux.
--with netperf-use-pstat: Enable code to perform HPUX CPU utilization. If use on HP-UX 10.0 and later, this will make CPU utilization measurements with some information returns by the 10.X pstat() call. This is very accurate, and should have no impact on the measurement. Astute observers will notices that the LOC_CPU and REM_CPU created with this method look remarkably close to the clock rate of the machine. This option defaults to ‘disabled’. Do not enable this option for Linux.
--with netperf-use-kstat: Enable code to Solaris CPU utilization. If used on Solaris 2, this will make CPU utilization measurments using the kstat() interface. This option defaults to ‘disabled’. Do not enable this option for Linux.
--without netperf-use-proc-stat: Disable use of /proc/stat interface. Enabled for Linux systems with CPU utilization info in /proc/stat. Provides a fairly accurate CPU load measurement without affecting measurement. This option defaults to ‘enabled’.
--with netperf-do-ipv6: Enables IPv6 testing. This option defaults to ‘disabled’.
--without netperf-do-dns: Disables DNS testing. This option defaults to ‘enabled’.
--with netperf-use-sysctl: Enables use of sysctl on BSD. When enabled, use the sysctl() call on FreeBSD (perhaps other BSDs) to calculate CPU utilization. This option defaults to ‘disabled’. Do not enable this option for Linux.
--with netperf-use-perfstat: Enable use of perfstat on AIX. When enabled, use the perfstat() call on AIX to calculate CPU utilization. This option defaults to ‘disabled’. Do not enable this option for Linux.
--with netperf-dont-wait: Enable MSG_DONTWAIT on sends. This option defaults to ‘disabled’.
--with-netperf-logfile=LOGFILE: Specify a debug log file. This option defaults to /tmp/netperf.debug.

In general, the default values of these options are sufficient for most purposes and no options need be provided when rebuilding the Source RPMs.

Build

To build from the source RPM, See Building from the Source RPM.

7.3.4 Configuring the Debian DSC

The Debian DSC can be configured by passing options in the environment variable BUILD_DEBOPTIONS. The options placed in this variable take the same form as those passed to the configure script, See Configuring the Tar Ball. For an example, See Building from the Debian DSC.

Build

To build from the Debian DSC, See Building from the Debian DSC.

7.3.5 Configuring the Tar Ball

All of the normal GNU autoconf(1) configuration options and environment variables apply. Additional options and environment variables are provided to tailor or customize the build and are described below.

7.3.5.1 Configure Options

This is a generic description of common configure options that are in addition to those provided by autoconf(1), automake(1), libtool(1) and gettext(1).

Not all configure options are applicable to all release packages. Options that are kernel module specific are only applicable to release packages that build kernel modules. STREAMS options are only applicable to release packages that provide or require STREAMS.

Following are the additional configure options, their meaning and use:

--enable-checks

--disable-checks

Enable or disable preinstall checks. Each release package supports a number of preinstall checks that can be performed by invoking the ‘check’ target with make(1). These currently consist of checking each kernel module for unresolved kernel symbols, checking for documentation for exported kernel module symbols, checking for documentation for exported library symbols, checking for standard options for build and installable programs, checking for documentation for built and installable programs. Normally these checks are only run in maintainer mode, but can be enabled and disabled with this option.

--disable-compress-manpages

Compress manual pages with ‘gzip -9’ or ‘bzip2 -9’ or leave them uncompressed. The default is to compress manual pages with ‘gzip -9’ or ‘bzip2 -9’ if a single compressed manual page exists in the target installation directory (--mandir). This disables automatic compression.

--disable-public

Disable public release. This option is not usable on public releases and only has a usable effect on OpenSS7 NETPERF Utility when the package is acquired from CVS. In particular, the STREAMS SS7/VoIP/ISDN/SIGTRAN Stacks (strss7-0.9a.8) release package has a large number of non-public components. Specifying this option will cause the package to build and install all private release components in addition to the public release components. This option affects all release packages. Most release packages do not have private release components.

--disable-initscripts

Disables the installation of init scripts. The default is to configure and install init scripts and their associated configuration files.

Although the default is to install init scripts, installation attempts to detect a System V init script configuration, and if one is not found, the init scripts are installed into the appropriate directories, but the symbolic links to the run level script directories are not generated and the script is not invoked. Therefore, it is safe to leave this option unchanged, even on distributions that do not support System V init script layout.

--disable-32bit-libs

Disables the build and install of 32-bit compatibility libraries and test binaries on 64-bit systems that support 32-bit compatibility. The default is to build and install 32-bit compatibility libraries and test binaries. This option can be usefule when configuring for an embedded target where only native shared libraries and binaries are desired.

--disable-devel

Disables the installation of development environment components such as header files, static libraries, manual pages and texinfo(1) documentation. The default is to install development environment components. This option can be useful when configuring for an embedded target where only the runtime components are desired, or when performing a edit-compile-test cycle.

--disable-docs

Disables the build and installation of major documentation such manual pages and texinfo(1) documentation. The default is to build and install documentation. This option can be useful when building for an embedded target where only the runtime and static compile components are desired, but not major documentation. This option does not override the setting of --disable-devel.

--enable-tools

Specifies whether user space programs and libraries are to be built and installed. The default is to build and install user space programs and libraries. This option can be useful when rebuilding for multiple architectures and target kernels, particularly under rpm(1) or dpkg(1). The ‘rebuild’ automake(1) target uses this feature when rebuilding RPMs for all available architectures and kernels, to rebuild user packages once per architecture instead of once per kernel.

--enable-modules

Specifies whether kernel modules are to be built and installed. The default is to build and install kernel modules. This option can be useful when rebuilding for multiple architectures and target kernels, particularly under rpm(1) or dpkg(1). The ‘rebuild’ automake(1) target uses this feature to rebuild for all available architectures and kernels. This option has no effect for release packages that do not provide kernel modules.

--enable-arch

Specifies whether architectural dependent package components are to be built and installed. This option can be useful when rebuilding for multiple architectures and target kernels, particularly under dpkg(1). The default is to configure, build and install architecture dependent package components. This option has no effect for release packages that do not provide architecture dependent components.

--enable-indep

Specifies whether architecture independent package components are to be built and installed. This option can be useful when rebuilding for multiple architectures and target kernels, particularly under dpkg(1). The default is to configure, build and install architecture independent package components. This options has no effect for release packages that do not provide architecture independent components.

--enable-k-inline

Enable kernel inline functions. Most Linux kernels build without -finline-functions. This option adds the -finline-functions and -Winline flags to the compilation of kernel modules. Use with care. This option has no effect for release packages that do not provide kernel modules.

--enable-k-safe

Enable kernel module run-time safety checks. Specifies whether kernel safety is to be performed. This option is mutually exclusive with --enable-k-test and --enable-k-debug below. This has the effect of invoking some more pedantic assertion macros in the code. The default is not to apply kernel safety. This option has no effect for release packages that have are no kernel modules.

--enable-k-test

Enable kernel module run-time testing. Specifies whether kernel testing is to be performed. This option is mutually exclusive with --enable-k-safe above and --enable-k-debug below. This has the effect of remove static and inline attributes from functions and invoking most non-performance affecting debugging macros in the code. The default is not to perform kernel testing. This option has no effect for release packages that do not provide kernel modules.

--enable-k-debug

Enable kernel module run-time debugging. Specifies whether kernel debugging is to be performed. This option is mutually exclusive with --enable-k-safe and --enable-k-test above. This has the effect of removing static and inline attributes from functions and invoking all debugging macros in the code (including performance-affecting debug macros). The default is to not perform kernel debugging. This option has no effect for release packages that do not provide kernel modules.

--disable-k-modversions

Disable module versions on netperf symbols. Specifies whether kernel symbol versions are to be used on symbols exported from built netperf modules. The default is to provide kernel symbol versions on all exported symbols. This option has no effect for release packages that do not provide kernel modules.

--enable-devfs

--disable-devfs

Specifies whether the build is for a device file system daemon enabled system with autoloading, or not. The default is to build for devfsd(8) autoloading when CONFIG_DEVFS_FS is defined in the target kernel. The ‘reuild’ automake(1) target uses this option to signal to the RPM spec file that the ‘dev’ subpackage need not be built. This option has no effect for release packages that do not provide devices.

--with-gpg-user=GNUPGUSER

Specify the gpg(1) ‘GNUPGUSER’ for signing RPMs and tarballs. The default is the content of the environment variable GNUPGUSER. If unspecified, the gpg(1) program will normally use the user name of the account invoking the gpg(1) program. For building source RPMs, the RPM macro ‘_gpg_name’ will override this setting.

--with-gpg-home=GNUPGHOME

Specify the ‘GNUPGHOME’ directory for signing RPMs and tarballs. The default is the user's ~/.gpg directory. For building source RPMs, the RPM macro ‘_gpg_path’ will override this setting.

--with-pkg-epoch=EPOCH

Specifies the epoch for the package. This is neither used for rpm(1) nor dpkg(1) packages, it applies to the tarball release as a whole. The default is the contents of the .pkgepoch file in the release package source directory or, if that file does not exist, zero (0).

--with-pkg-release=RELEASE

Specifies the release for the package. This is neither used for rpm(1) nor dpkg(1) packages, it applies to the tarball release as a whole. The default is the contents of the .pkgrelease file in the release package source directory or, if that file does not exist, one (1). This is the number after the last point in the package version number.

--with-pkg-distdir=DIR

Specifies the distribution directory for the package. This is used by the maintainer for building distributions of tarballs. This is the directory into which archives are copied for distribution. The default is the top build directory.

--with-cooked-manpages

Convert manual pages to remove macro dependencies and grefer(1) references. Some systems do not like grefer(1) references in manual pages.²⁷ This option will cook soelim(1), refer(1), tbl(1) and pic(1) commands from the manual pages and also strip groff(1) comments. The default is to leave manual pages uncooked (they are actually smaller that way).

--with-rpm-epoch=PACKAGE_EPOCH

Specify the ‘PACKAGE_EPOCH’ for the RPM spec file. The default is to use the RPM epoch contained in the release package file .rpmepoch.

--with-rpm-release=PACKAGE_RPMRELEASE

Specify the ‘PACKAGE_RPMRELEASE’ for the RPM spec file. The default is to use the RPM release contained in the release package file .rpmrelease.

--with-rpm-extra=PACKAGE_RPMEXTRA

Specify the ‘PACKAGE_RPMEXTRA’ extra release information for the RPM spec file. The default is to use the RPM extra release information contained in the release package file .rpmextra. Otherwise, this value will be determined from automatic detection of the RPM distribution.

--with-rpm-topdir=PACKAGE_RPMTOPDIR

Specify the ‘PACKAGE_RPMTOPDIR’ top directory for RPMs. If specified with a null ‘PACKAGE_RPMTOPDIR’, the default directory for the RPM distribution will be used. If this option is not provided on the command line, the top build directory will be used as the RPM top directory as well.

--with-deb-epoch=EPOCH

Specify the ‘PACKAGE_DEBEPOCH’ for the DEB control file. The default is to use the DEB epoch contained in the release package file .debepoch.

--with-deb-release=RELEASE

Specify the ‘PACKAGE_DEBRELEASE’ for the DEB control file. The default is to use the DEB release contained in the release package file .debrelease.

--with-deb-topdir=DIR

Specify the ‘PACKAGE_DEBTOPDIR’ top directory for DEBs. If specified with a null ‘PACKAGE_DEBTOPDIR’, the default directory for the DEB distribution will be used. If this option is not provided on the command line, the top build directory will be used as the DEB top directory as well.

--with-k-release=PACKAGE_KRELEASE

Specify the ‘PACKAGE_KRELEASE’ release of the Linux kernel for which the build is targeted. When not cross compiling, if this option is not set, the build will be targeted at the kernel running in the build environment (e.g., ‘uname -r’). When cross-compiling this option must be specified or the configure script will generate an error and terminate.

--with-k-linkage=PACKAGE_KLINKAGE

Specify the ‘PACKAGE_KLINKAGE’ for kernel module linkage. This can be one of the following:

‘loadable’ – loadable kernel modules
‘linkable’ – linkable kernel objects

The default is to build loadable kernel modules.

--with-k-modules=K-MODULES-DIR

Specify the ‘K-MODULES-DIR’ directory to which kernel modules will be installed. The default is based on the option --with-k-release, --with-k-prefix and --with-k-rootdir. The default is DESTDIR/K-MODULES-DIR which is typically DESTDIR/lib/modules/PACKAGE_KRELEASE/. This directory is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message.

--with-k-build=K-BUILD-DIR

Specify the ‘K-BUILD-DIR’ base kernel build directory in which configured kernel source resides. The default is DESTDIR/K-MODULES-DIR/build. This directory is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message.

--with-k-source=K-SOURCE-DIR

Specify the ‘K-SOURCE-DIR’ base kernel build directory in which configured kernel source resides. The default is DESTDIR/K-MODULES-DIR/source. This directory is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message.

--with-k-modver=K-MODVER-FILE

Specify the ‘K-MODVER-FILE’ kernel module versions file. The default is K-BUILD-DIR/Module.symvers. This file is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message.

--with-k-sysmap=K-SYSMAP-FILE

Specify the ‘K-SYSMAP-FILE’ kernel system map file. The default is K-BUILD-DIR/System.map. This file is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message.

--with-k-archdir=K-ARCHDIR

Specify the ‘K-ARCHDIR’ kernel source architecture specific directory. The default is DESTDIR/K-SOURCE-DIR/arch. This directory is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message.

--with-k-machdir=K-MACHDIR

Specify the ‘K-MACHDIR’ kernel source machine specific directory. The default is DESTDIR/K-SOURCE-DIR/target_cpu. This directory is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message.

--with-k-config=K-CONFIG

Specify the ‘K-CONFIG’ kernel configuration file. The default is BOOT/config-K-RELEASE. This configuration file is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message.

--with-k-optimize=HOW

--without-k-optimize

Specify ‘HOW’ optimization, normal, size, speed or quick. size compiles kernel modules -Os, speed compiles kernel modules -O3, and quick compiles kernel modules -O0. The default is normal. Use with care. The most common use of this option is to specify --with-k-optimize=speed --disable-k-safe to compile for maximum performance. Nevertheless, even these setting are ricing and the resulting kernel modules will only be about 5% faster.

--with-lis[=LIS-DIR]

--without-lis

Specify the ‘LIS-DIR’ directory in which to find LiS headers. Also specifies that the build is to be made against Linux STREAMS. The default is /usr/include/LiS if it exists, ‘no’ otherwise. This directory is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message. This option has no effect on release packages that do not use the STREAMS subsystem.

--with-lfs[=LFS-DIR]

--without-lfs

Specify the ‘LFS-DIR’ directory in which to find LfS headers. Also specifies that the build is to be made against Linux Fast-STREAMS. The default is /usr/include/streams if it exists, ‘no’ otherwise. This directory is normally located by the configure script and need only be provided for special cross-build environments or when requested by a configure script error message. This option has no effect on release packages that do not use the STREAMS subsystem.

--with-strconf-master=STRCONF_CONFIG

Specify the ‘STRCONF_CONFIG’ file name to which the configuration master file is written. The default is Config.master. This option has no effect on release packages that do not use the STREAMS subsystem and the strconf scripts. This option should not be specified when configuring the master package as the setting for all add-on packages will conflict.

--with-base-major=STRCONF_MAJBASE

Start numbering for major devices at ‘STRCONF_MAJBASE’. The default is ‘230’. This option has no effect on release packages that do not use the STREAMS subsystem and the strconf scripts. This option should not be specified when configuring the master package as the setting for all add-on packages will conflict.

In addition, the following configure options, specific to the OpenSS7 NETPERF Utility package are available:

--disable-netperf-dirty: Disable code that dirties buffers before calls to send. This option defaults to ‘enabled’.
--disable-netperf-histogram: Disable code to keep a histogram of request-response times or time spend in send(). This option defaults to ‘enabled’.
--enable-netperf-old-histogram: Enable old pre-2.2pl6 formatted histogram. This option defaults to ‘disabled’.
--disable-netperf-intervals: Disable code to allow pacing of sends in UDP, TCP or SCTP tests. This may have unexpected results on non-HPUX systems. This option defaults to ‘enabled’.
--disable-netperf-do-dlpi: Disable code to test to the DLPI implementation. This option defaults to ‘enabled’.
--disable-netperf-do-sctp: Disable code to test the SCTP implementation. This option defaults to ‘enabled’.
--disable-netperf-do-select: Disable code to do select() on receive. This option defaults to ‘enabled’.
--enable-netperf-do-lwp: This option defaults to ‘disabled’.
--disable-netperf-do-nbrr: Disable code to do non-blocking request-response. This option defaults to ‘enabled’.
--disable-netperf-do-xti: Disable code to test the XTI implementation. This option defaults to ‘enabled’.
--disable-netperf-do-xti-sctp: Disable code to test the XTI SCTP implementation. This option defaults to ‘enabled’.
--disable-netperf-do-unix: Disable code to test the UNIX domain implementation. This option defaults to ‘enabled’.
--disable-netperf-do-1644: Disable code to test T/TCP vs TCP transactions. This option defaults to ‘enabled’.
--disable-netperf-do-first-burst: Disable code to create an initial burst. This option defaults to ‘enabled’.
--enable-netperf-use-looper: Enable looper or soaker processes. When enabled, use looper or soaker processes to measure CPU utilization. These will be forked-off at the beginning. If you are running this way, it is important to see how much impact these have on the measurement. A loop back test on uniprocessor should be able to consume approximately 100% of the CPU, and the difference between throughput with USE_LOOPER_CPU and without should be small for a real network. If it is not, then some work probably needs to be done on reducing the priority of the looper processes. This option defaults to ‘disabled’. Do not enable this option for Linux.
--enable-netperf-use-pstat: Enable code to perform HPUX CPU utilization. If use on HP-UX 10.0 and later, this will make CPU utilization measurements with some information returns by the 10.X pstat() call. This is very accurate, and should have no impact on the measurement. Astute observers will notice that the LOC_CPU and REM_CPU created with this method look remarkably close to the clockrate of the machine. This option defaults to ‘disabled’. Do not enable this option for Linux.
--enable-netperf-use-kstat: Enable code to Solaris CPU utilization. If used on Solaris 2, this will make CPU utilization measurements using the kstat() interface. This option defaults to ‘disabled’. Do not enable this option for Linux.
--disable-netperf-use-proc-stat: Disable use of /proc/stat interface. Enabled for Linux systems with CPU utilization info in /proc/stat. Provides a fairly accurate CPU load measurement without affecting measurement. This option defaults to ‘enabled’.
--enable-netperf-do-ipv6: Enables IPv6 testing. This option defaults to ‘disabled’.
--disable-netperf-do-dns: Disables DNS testing. This option defaults to ‘enabled’.
--enable-netperf-use-sysctl: Enables use of sysctl on BSD. When enabled, use the sysctl() call on FreeBSD (perhaps other BSDs) to calculate CPU utilization. This option defaults to ‘disabled’. Do not enable this option for Linux.
--enable-netperf-use-perfstat: Enable use of perfstat on AIX. When enabled, use the perfstat() call on AIX to calculate CPU utilization. This option defaults to ‘disabled’. Do not enable this option for Linux.
--enable-netperf-dont-wait: Enable MSG_DONTWAIT on sends. This option defaults to ‘disabled’.
--with-netperf-logfile=LOGFILE: Specify a debug log file. This option defaults to /tmp/netperf.debug.

7.3.5.2 Environment Variables

Following are additional environment variables to configure, their meaning and use:

GPG: GPG signature command. This is used for signing distributions by the maintainer. By default, configure will search for this tool.
GNUPGUSER: GPG user name. This is used for signing distributions by the maintainer.
GNUPGHOME: GPG home directory. This is used for signing distributions by the maintainer.
GPGPASSWD: GPG password for signing. This is used for signing distributions by the maintainer. This environment variable is not maintained by the configure script and should only be used on an isolated system.
SOELIM: Roff source elimination command, soelim(1). This is only necessary when the option --with-cooked-manpages has been specified and configure cannot find the proper soelim(1) command. By default, configure will search for this tool.
REFER: Roff references command, refer(1). This is only necessary when the option --with-cooked-manpages has been specified and configure cannot find the proper refer(1) command. By default, configure will search for this tool.
TBL: Roff table command, tbl(1). This is only necessary when the option --with-cooked-manpages has been specified and configure cannot find the proper tbl(1) command. By default, configure will search for this tool.
PIC: Roff picture command, pic(1). This is only necessary when the option --with-cooked-manpages has been specified and configure cannot find the proper pic(1) command. By default, configure will search for this tool.
GZIP: Default compression options provided to GZIP_CMD.
GZIP_CMD: Manpages (and kernel modules) compression commands, gzip(1). This is only necessary when the option --without-compressed-manpages has not been specified and configure cannot find the proper gzip(1) command. By default, configure will search for this tool.
BZIP2: Default compression options provided to BZIP2_CMD
BZIP2_CMD: Manpages compression commands, bzip2(1). This is only necessary when the option --without-compressed-manpages has not been specified and configure cannot find the proper bzip2(1) command. By default, configure will search for this tool.
MAKEWHATIS: Manpages apropros database rebuild command, makewhatis(8). By default, configure will search for this tool. By default, configure will search for this tool.
CHKCONFIG: Chkconfig command, chkconfig(8). This was used for installation of init scripts. All packages now come with init_install(8) and init_remove(8) scripts used to install and remove init scripts on both RPM and Debian systems.
RPM: Rpm command, rpm(1). This is only necessary for RPM builds. By default, configure will search for this tool.
RPMBUILD: Build RPM command, rpmbuild(1). This is only necessary for RPM builds. By default, configure will search for this tool. rpm(1) will be used instead of rpmbuild(1) only if rpmbuild(1) cannot be found.
DPKG: Dpkg comand, dpkg(1). This command is used for building Debian packages. By default, configure will search for this tool.
DPKG_SOURCE: Dpkg-source command, dpkg-source(1). This command is used for building Debian dsc packages. By default, configure will search for this tool.
DPKG_BUILDPACKAGE: Dpkg-buildpackage command, dpkg-buildpackage(1). This command is used for building Debian deb packages. By default, configure will search for this tool.
DEB_BUILD_ARCH: Debian build architecture. This variable is used for building Debian packages. The default is the autoconf build architecture.
DEB_BUILD_GNU_CPU: Debian build cpu. This variable is used for building Debian packages. The default is the autoconf build cpu.
DEB_BUILD_GNU_SYSTEM: Debian build os. This variable is used for building Debian packages. The default is the autoconf build os.
DEB_BUILD_GNU_TYPE: Debian build alias. This variable is used for building Debian packages. The default is the autoconf build alias.
DEB_HOST_ARCH: Debian host architecture. This variable is used for building Debian packages. The default is the autoconf host architecture.
DEB_HOST_GNU_CPU: Debian host cpu. This variable is used for building Debian packages. The default is the autoconf host cpu.
DEB_HOST_GNU_SYSTEM: Debian host os. This variable is used for building Debian packages. The default is the autoconf host os.
DEB_HOST_GNU_TYPE: Debian host alias. This variable is used for building Debian packages. The default is the autoconf host alias.
LDCONFIG: Configure loader command, ldconfig(8). Command used to configure the loader when libraries are installed. By default, configure will search for this tool.
DESTDIR: Cross build root directory. Specifies the root directory for build and installation.
DEPMOD: Build kernel module dependencies command, depmod(8). This is used during installation of kernel modules to a running kernel to rebuild the modules dependency database. By default, configure will search for this tool.
MODPROBE: Probe kernel module dependencies command, modprobe(8). This is used during installation of kernel modules to a running kernel to remove old modules. By default, configure will search for this tool.
LSMOD: List kernel modules command, lsmod(8). This is used during installation of kernel modules to a running kernel to detect old modules for removal. By default, configure will search for this tool.
LSOF: List open files command, lsof(1). This is used during installation of kernel modules to a running kernel to detect old modules for removal. Processes owning the old kernel modules will be killed and the module removed. If the process restarts, the new module will be demand loaded. By default, configure will search for this tool.
GENKSYMS: Generate kernel symbols command, genksyms(8). This is used for generating module symbol versions during build. By default, configure will search for this tool.
KGENKSYMS: Linux 2.6 generate kernel symbols command, genksyms(8). This is used for generating module symbol version during build. By default, configure will search for this tool.
OBJDUMP: Object dumping command, objdump(1). This is used for listing information about object files. By default, configure will search for this tool.
NM: Object symbol listing command, nm(1). This is used for listing information about object files. By default, configure will search for this tool.
MODPOST_CACHE: Cache file for modpost(1). The version of the modpost.sh script that ships with each package can cache information to a cache file to speed multiple builds. This environment variable is used to specify a cache file.
AUTOM4TE: Autom4te command, autom4te(1). This is the executable used by autotest for pre- and post-installation checks. By default, configure will search for this tool.
AUTOTEST: Autotest macro build command, autom4te(1). This is the executable used by autotest for pre- and post-installation checks. By default, configure will search for this tool.

7.3.5.3 Build

To build from the tar ball, See Building from the Tar Ball.

7.4 Building

7.4.1 Building from the Source RPM

If you have downloaded the necessary source RPM (see Downloading the Source RPM), then the following instructions will rebuild the binary RPMs on your system. Once the binary RPMs are rebuilt, you may install them as described above (see Installing the Binary RPM).

The source RPM is rebuilt to binary RPMs as follows:

     % wget http://www.openss7.org/rpms/SRPMS/netperf-2.3.7-1.src.rpm
     % rpmbuild --rebuild -vv netperf-2.3.7-1.src.rpm

The rebuild process can also recognize a number of options that can be used to tweak the resulting binaries, See Configuring the Source RPM. These options are provided on the rpm(1) command line. For example:

     % rpmbuild --rebuild -vv --target athlon-redhat-linux \
       --with lis -- netperf-2.3.7-1.src.rpm

will rebuild binary RPM for the ‘athlon’ architecture against the LiS STREAMS package.

Installation

To install the resulting binary RPM, See Installing the Binary RPM.

7.4.2 Building from the Debian DSC

If you have downloaded the necessary Debian DSC (see Downloading the Debian DSC), then the following instructions will rebuild the binary DEBs on your system. Once the binary DEBs are rebuilt, you may install them as described above (see Installing the Debian DEB).

The Debian DSC is rebuilt to binary DEBs as follows:

     % wget http://www.openss7.org/debian/netperf_2.3.7-0.dsc
     % wget http://www.openss7.org/debian/netperf_2.3.7-0.tar.gz
     % dpkg-buildpackage -v netperf_2.3.7-0.dsc

The rebuild process can also recognize a number of options that can be used to tweak the resulting binaries, See Configuring the Debian DSC. These options are provided in the environment variable BUILD_DPKGOPTIONS and have the same form as the options to configure, See Configuring the Tar Ball. For example:

     % BUILD_DEBOPTIONS='
             --with-lis
             --host=athlon-debian-linux-gnu'
       dpkg-buildpackage -v \
       netperf_2.3.7-0.dsc

will rebuild binary DEB for the ‘athlon’ architecture against the LiS STREAMS package.

Installation

To install the resulting binary DEB, See Installing the Debian DEB.

7.4.3 Building from the Tar Ball

If you have downloaded the tar ball (see Downloading the Tar Ball), then the following instructions will rebuild the package on your system. (Note that the build process does not required root privilege.)

7.4.3.1 Native Build

Following is an example of a native build against the running kernel:

     % wget http://www.openss7.org/netperf-2.3.7.tar.bz2
     % tar -xjvf netperf-2.3.7.tar.bz2
     % pushd netperf-2.3.7
     % ./configure
     % make
     % popd

7.4.3.2 Cross-Build

Following is an example for a cross-build. The kernel release version must always be specified for a cross-build.²⁸ If you are cross-building, specify the root for the build with environment variable DESTDIR. The cross-compile host must also be specified if different from the build host. Either the compiler and other tools must be in the usual places where GNU autoconf(1) can find them, or they must be specified with declarations such as ‘CC=/usr/lib/ppc-linux/gcc’ on the configure command line.

     % wget http://www.openss7.org/netperf-2.3.7.tar.bz2
     % tar -xjvf netperf-2.3.7.tar.bz2
     % pushd netperf-2.3.7
     % ./configure DESTDIR="/some/other/root" \
     	--with-k-release=2.4.18 --host sparc-linux
     % make
     % popd

7.5 Installing

7.5.1 Installing the Binary RPM

If you have downloaded the necessary binary RPMs (see Downloading the Binary RPM), or have rebuilt binary RPMs using the source RPM (see Building from the Source RPM), then the following instructions will install the RPMs on your system. For additional information on rpm(1), see rpm(8).

     % pushd RPMS/i686
     % rpm -ihv netperf-*-2.3.7-1.7.2.i686.rpm

You must have the correct binary RPMs downloaded or built for this to be successful.

Some of the packages are relocatable and can have final installation directories altered with the --relocate option to rpm(1), see rpm(8). For example, the following will relocate the documentation and info directories:

     % pushd RPMS/i686
     % rpm -ihv \
             --relocate '/usr/share/doc=/usr/local/share/doc' \
             --relocate '/usr/share/info=/usr/local/share/info' \
             -- netperf-doc-2.3.7-1.7.2.i686.rpm

The previous example will install the netperf-doc package by will relocate the documentation an info directory contents to the /usr/local version.

7.5.2 Installing the Debian DEB

If you have downloaded the necessary Debian DEBs (see Downloading the Debian DEB), or have rebuild binary DEBs using the Debian DSC (see Building from the Debian DSC), then the following instructions will install the DEBs on your system. For additional information see dpkg(8).

     % pushd debian
     % dpkg -iv netperf-*_2.3.7-0_*.deb

You must have the correct .deb files downloaded or build for this to be successful.

7.5.3 Installing the Tar Ball

After the build process (see Building from the Tar Ball), installation only requires execution of one of two automake(1) targets:

‘make install’: The ‘install’ automake(1) target will install all the components of the package. Root privilege is required to successfully invoke this target.
‘make install-strip’: The ‘install-strip’ automake(1) target will install all the components of the package, but will strip unnecessary information out of the objects and compress manual pages. Root privilege is required to successfully invoke this target.

7.6 Removing

7.6.1 Removing the Binary RPM

To remove an installed version of the binary RPMs (whether obtained from the OpenSS7 binary RPM releases, or whether created by the source RPM), execute the following command:

     % rpm -evv `rpm -qa | grep '^netperf-'`

For more information see rpm(1).

7.6.2 Removing the Debian DEB

To remove and installed version of the Debian DEB (whether obtained from the OpenSS7 binary DEB releases, or whether created by the Debian DSC), execute the following command:

     % dpkg -ev `dpkg -l | grep '^netperf-'`

For more information see dpkg(8).

7.6.3 Removing the Source RPM

To remove all the installed binary RPM build from the source RPM, see Removing the Binary RPM. Then simply remove the binary RPM package files and source RPM file. A command such as:

     % find / -name 'netperf-*.rpm' -type f -print0 | xargs --null rm -f

should remove all netperf RPMs from your system.

7.6.4 Removing the Debian DSC

To remove all the installed binary DEB build from the Debian DSC, see Removing the Debian DEB. Then simply remove the binary DEB package files and Debian DSC file. A command such as:

     % find / \( -name 'netperf-*.deb' \
              -o -name 'netperf-*.dsc' \
              -o -name 'netperf-*.tar.* \
              \) -type f -print0 | xargs --null rm -f

should remove all netperf DEBs, DSCs and TARs from your system.

7.6.5 Removing the Tar Ball

To remove a version installed from tar ball, change to the build directory where the package was built and use the ‘uninstall’ automake(1) target as follows:

     % cd /usr/src/netperf
     % make uninstall
     % cd ..
     % rm -fr netperf-2.3.7
     % rm -f netperf-2.3.7.tar.gz
     % rm -f netperf-2.3.7.tar.bz2

If you have inadvertently removed the build directory and, therefore, no longer have a configured directory from which to execute ‘make uninstall’, then perform all of the steps for configuration and installation (see Installing the Tar Ball) except the final installation and then perform the steps above.

7.6.5.1 Linux STREAMS Module Loading

LiS is deprecated and this section has been deleted.

7.7 Maintenance

7.7.1 Makefile Targets

automake(1) has many targets, not all of which are obvious to the casual user. In addition, OpenSS7 automake(1) files have additional rules added to make maintaining and releasing a package somewhat easier. This list of targets provides some help with what targets can be invoked, what they do, and what they hope to achieve. The available targets are as follows:

7.7.1.1 User Targets

The following are normal targets intended to be invoked by installers of the package. They are concerned with compiling, checking the compile, installing, checking the installation, and removing the package.

‘[all]’

This is also the default target. It compiles the package and all release packages selected by configure. This is performed after configuring the source with ‘configure’. A Makefile stub is provided so that if the package has not had autoreconf(1) run (such as when checked out from CVS, the package will attempt to run ‘autoreconf -fiv’.

All OpenSS7 Project packages are configured without maintainer mode and without dependency tracking by default. This speeds compilation of the package for one-time builds. This also means that if you are developing using the source package (edit-compile-test cycle), changes made to source files will not cause the automatic rebuilding due to dependencies. There are two ways to enable dependency tracking: specify --enable-maintainer-mode to configure; or, specify --enable-dependency-tracking to configure. I use the former during my edit-compile-test cycle.

This is a standard GNU automake(1) makefile target. This target does not require root privilege.

‘check’

All OpenSS7 Project release packages provide check scripts for the check target. This step is performed after compiling the package and will run all of the ‘check’ programs against the compiled binaries. Which checks are performed depends on whether --enable-maintainer-mode was specified to configure. If in maintainer mode, checks that assist with the release of the package will be run (such as checking that all manual pages load properly and that they have required sections.) We recommend running the check stage before installing, because it catches problems that might keep the installed package from functioning properly.

Another way to enable the greater set of checks, without invoking maintainer mode, is to specify --enable-checks to configure. For more information, see Pre-installation Checks.

This is a standard GNU automake(1) makefile target, although the functions performed are customized for the OpenSS7 Project. This target does not require root privilege.

‘install’

‘install-strip’

The ‘install’ target installs the package by installing each release package. This target also performs some actions similar to the pre- and post-install scripts used by packaging tools such as rpm(1) or dpkg(1). The ‘install-strip’ target strips unnecessary symbols from executables and kernel modules before installing.

This is a standard GNU automake(1) makefile target. This target requires root privilege.

‘installcheck’

All OpenSS7 Project packages provide test scripts for the ‘installcheck’ target. Test scripts are created and run using autotest (part of the autoconf(1) package). Which test suites are run and how extensive they are depends on whether --enable-maintainer-mode was specified to configure. When in maintainer mode, all test suites will be run. When not in maintainer mode, only a few post-install checks will be performed, but the test suites themselves will be installed in /usr/libexec/netperf²⁹ for later use.

This is a standard GNU automake(1) makefile target. This target might require root privilege. Tests requiring root privilege will be skipped when run as a regular user. Tests requiring regular account privileges will be skipped when run as root.

‘retest’

To complement the ‘installcheck’ target above, all OpenSS7 Project packages provide the ‘retest’ target as a means to rerun failed conformance test suite test cases. The ‘retest’ target is provided because some test cases in the test suites have delicate timing considerations that allow them to fail sporadically. Invoking this target will retest the failed cases until no cases that are not expected failures remain.

This is an OpenSS7 Project specific makefile target. As with ‘installcheck’, this target might require root privilege. Tests requiring root privilege will be skipped when run as a regular user. Tests requiring regular account privileges will be skipped when run as root.

‘uninstall’

This target will reverse the steps taken to install the package. This target also performs pre- and post- erase scripts used by packaging tools such as rpm or dpkg. You need to have a configured build directory from which to execute this target, however, you do not need to have compiled any of the files in that build directory.³⁰

The ‘uninstall’ target unfortunately removes add-on packages in the same order in which they were installed. This is not good for the OpenSS7 Master Package, where the ‘remove’ target should be used instead.

This is a standard GNU automake(1) makefile target. This target requires root privilege.

‘remove’

This target is like ‘uninstall’ with the exception that it removes add-on packages in the reverse order that installation was performed.³¹

This is an OpenSS7 Project specific makefile target. This target requires root privilege.

7.7.1.2 Maintainer Targets

The following targets are targets intended for use by maintainers of the package, or those responsible for release and packaging of a derivative work of the package. Some of these targets are only effective when maintainer mode has been invoked (--enable-maintainer-mode specified to configure.)

‘dist’: Creates a distribution package (tarball) in the top level build directory. OpenSS7 Project packages distribute two archives: a ‘gzip tar’ archive and a ‘bzip tar’ archive. These archives will have the name netperf-2.3.7.tar.gz and netperf-2.3.7.tar.bz2.
This is a standard GNU automake(1) makefile target. This target does not require root privilege.
‘distcheck’: This target is intended for use when releasing the package. It creates the tar(1) archives above and then unpacks the tarball in a source directory, configures in a separate build directory, compiles the package, installs the package in a separate install directory, tests the install package to ensure that some components work, and, finally, uses the unpacked source tree to build another tarball. If you have added or removed files from the package, this is a good way to ensure that everything is still stable for release.
This is a standard GNU automake(1) makefile target. This target does not require root privilege.

7.7.1.3 Clean Targets

‘mostlyclean’: Cleans out most of the files from the compile stage. This target is helpful if you have not enabled dependency tracking and need to recompile with changes.
This is a standard GNU automake(1) makefile target. This target does not require root privilege.
‘clean’: Cleans all the files from the build directory generated during the ‘make [all]’ phase. It does not, however, remove files from the directory left there from the configure run. Use the ‘distclean’ target to remove those too.
This is a standard GNU automake(1) makefile target. This target might require root privilege if the ‘installcheck’ target or the testsuite was invoked with root privilege (leaving files belonging to root).
‘distclean’: This target cleans out the directories left behind by ‘distcheck’ and removes all the configure and generated files from the build directory. This will effectively remove all the files in the build directory, with the except of files that belong to you or some other process.
This is a standard GNU automake(1) makefile target. This target might require root privilege if the ‘installcheck’ target or the testsuite was invoked with root privilege (leaving files belonging to root).
‘maintainer-clean’: This target not only removes files from the build directory, it removes generated files from the source directory as well. Care should be taken when invoking this target, because it removes files generated by the maintainer and distributed with the archive that might require special tools to regenerate. These special tools might only be available to the maintainer.³² It also means that you probably need a full blown Linux system to rebuild the package. For more information, see Downloading from CVS.
This is a standard GNU automake(1) makefile target. This target might require root privilege if the ‘installcheck’ target or the testsuite was invoked with root privilege (leaving files belonging to root).
‘check-clean’: This target removes log files left behind by the ‘check’ target. By default, the check scripts append to log files in the top level build directory. This target can be used to clean out those log files before the next run.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

7.7.1.4 Manual Page Targets

The following targets are used to build, install and uninstall just the manual pages from the distribution. These targets are good for creating a distribution of just the manual pages. When building atop multiple packages, these targets recurse down through each package.

‘mans’: Build all of the manual pages. This involves performing parameter substitution on manual pages and optionally cooking the manual pages if --with-cooked-manpages was requested during configuration.
‘install-mans’: Installs the manual pages under DESTDIR. Specify DESTDIR to place the manual pages wherever you see fit. If DESTDIR is not specified on the command line, the manual pages will be installed in the normal installation directory.
‘uninstall-mans’: Uninstalls the manual pages from DESTDIR. Specify DESTDIR to indicate where to remove the manual pages from. If DESTDIR is not specified on the command line, the manual pages will be removed from the normal installation directory.

7.7.1.5 Release Targets

The following are targets used to generate complete releases into the package distribution directory. These are good for unattended and NFS builds, which is what I use them for. Also, when building from atop multiple packages, these targets also recurse down through each package.

‘release’: Build all of the things necessary to generate a release. On an rpm(1) system this is the distribution archives, the source rpm, and the architecture dependent and architecture independent binary rpms. All items are placed in the package distribution directory that can be specified with the --with-pkg-distdir=DIR option to configure.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.
‘forced-release’: The ‘release’ target will not regenerate any files that already exist in the package distribution directory. This forced target will.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.
‘release-sign’: You will be prompted for a password, unless to specify it to make with the GNUPGPASS variable. For unattended or non-interactive builds with signing, you can do that as: ‘make GNUPGPASS=mypasswd release-sign’
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.
‘forced-release-sign’: The ‘release-sign’ target will not regenerate any files that already exist in the package distribution directory. This forced target will.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.
‘release-clean’: This target will remove all distribution files for the current package from the package distribution directory.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

7.7.1.6 Logging Targets

For convenience, to log the output of a number of targets to a file, log targets are defined. The log file itself is used as the target to make, but make invokes the target minus a .log suffix. So, for example, to log the results of target ‘foo’, invoke the target ‘foo.log’. The only target that this does not apply to is ‘compile.log’. When you invoke the target ‘compile.log’ a simple automake(1) is invoked and logged to the file compile.log. The ‘foo.log’ rule applies to all other targets. This does not work for all targets, just a selected few.³³ Following are the logging targets:

Common Logging Targets

Common logging targets correspond to normal user automake(1) makefile targets as follows:

‘compile.log’: This is an OpenSS7 Project specific makefile target, but it invokes the standard GNU automake(1) makefile target ‘[all]’.
‘check.log’: This is an OpenSS7 Project specific makefile target, but it invokes the standard GNU automake(1) makefile target ‘check’.
‘install.log’: This is an OpenSS7 Project specific makefile target, but it invokes the standard GNU automake(1) makefile target ‘install’.
‘installcheck.log’: This is an OpenSS7 Project specific makefile target, but it invokes the standard GNU automake(1) makefile target ‘installcheck’.
‘uninstall.log’: This is an OpenSS7 Project specific makefile target, but it invokes the standard GNU automake(1) makefile target ‘uninstall’.
‘remove.log’: This is an OpenSS7 Project specific makefile target, that invokes the OpenSS7 Project ‘remove’ target.

Maintainer Logging Targets

Maintainer logging targets correspond to maintainer mode automake(1) makefile targets as follows:

‘dist.log’: This is an OpenSS7 Project specific makefile target, but it invokes the standard GNU automake(1) makefile target ‘dist’.
‘distcheck.log’: This is an OpenSS7 Project specific makefile target, but it invokes the standard GNU automake(1) makefile target ‘distcheck’.
‘srpm.log’: This is an OpenSS7 Project specific makefile target, that invokes the OpenSS7 Project ‘srpm’ target.
‘rebuild.log’: This is an OpenSS7 Project specific makefile target, that invokes the OpenSS7 Project ‘rebuild’ target.
‘resign.log’: This is an OpenSS7 Project specific makefile target, that invokes the OpenSS7 Project ‘resign’ target.
‘release.log’: This is an OpenSS7 Project specific makefile target, that invokes the OpenSS7 Project ‘release’ target.
‘release-sign.log’: This is an OpenSS7 Project specific makefile target, that invokes the OpenSS7 Project ‘release-sign’ target.

If you want to add one, simply add it to LOGGING_TARGETS in Makefile.am.

7.7.1.7 Problem Report Targets

To ease problem report generation, all logging targets will automatically generate a problem report suitable for mailing in the file target.pr for target ‘target.log’. This problem report file is in the form of an email and can be sent using the included send-pr script or by invoking the ‘send-pr’ makefile target.

There are two additional problem report targets:

‘pr’: The ‘pr’ target is for independently generating a problem report outside of the build or installation process. The target will automatically generate a problem report skeleton suitable for editing and mailing in the file problem.pr. This problem report file is in the form of an email and can be edited and sent directly, or sent using the included send-pr script or by invoking the ‘send-pr’ target.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.
‘send-pr’: The ‘send-pr’ target is for finalizing and mailing a problem report generated either inside or outside the build and installation process. The target will automatically finalize and mail the problem.pr problem report if it has changed since the last time that ‘send-pr’ was invoked.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege (unless the problem report file was generated as root).

7.7.1.8 Release Archive Targets

The following targets are used to generate and clean distribution archive and signature files. Whereas the ‘dist’ target affects archives in the top build directory, the ‘release-archive’ targets affects archives in the package distribution directory (either the top build directory or that specified with --with-pkg-distdir=DIR to configure).

You can change the directory to which packages are distributed by using the --with-pkg-distdir=DIR option to configure. The default directory is the top build directory.

‘release-archives’

This target creates the distribution archive files if they have not already been created. This not only runs the ‘dist’ target, but also copies the files to the distribution directory, which, by default is the top build directory.

The files generated are named:

netperf-2.3.7.tar.gz and netperf-2.3.7.tar.bz2

You can change this distribution directory with the --with-pkg-distdir option to configure. See ‘./configure --help’ for more details on options.

This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

‘release-sign-archives’

This target is like ‘release-archives’, except that it also signs the archives using a GPG detached signature. You will be prompted for a password unless you pass the GNUPGPASS variable to make. For automated or unattended builds, pass the GNUPGPASS variable like so:

‘make GNUPGPASS=mypasswd release-sign-archives’

Signature files will be named:

netperf-2.3.7.tar.gz.asc and netperf-2.3.7.tar.bz2.asc

These files will be moved to the package distribution directory with the plain text archives.

This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

‘release-clean-archives’

This target will clean the release archives and signature files from the package distribution directory.

This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

7.7.1.9 RPM Build Targets

On rpm(1) systems, or systems sporting rpm packaging tools, the following targets are used to generate rpm(1) release packages. The epoch and release number can be controlled by the contents of the .rpmepoch and .rpmrelease files, or with the --with-rpm-epoch=EPOCH and --with-rpm-release=RELEASE options to configure. See ‘configure --help’ for more information on options. We always use release number ‘1’. You can use release numbers above ‘1’.

‘srpm’

This target generates the source rpm for the package (without signing the source rpm). The source rpm will be named: netperf-2.3.7-1.srpm.

This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

‘rpms’

This target is responsible for generating all of the package binary rpms for the architecture. The binary rpms will be named:

netperf-*-2.3.7-1.*.rpm

where the stars indicate the subpackage and the architecture. Both the architecture specific subpackages (binary objects) and the architecture independent (.noarch) subpackages will be built unless the the former was disabled with the option --disable-arch, or the later with the option --disable-indep, passed to configure.

This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

‘sign’

‘srpm-sign’

These two targets are the same. When invoked, they will add a signature to the source rpm file, provided that the file does not already have a signature. You will be prompted for a password if a signature is required. Automated or unattended builds can be achieved by using the emake expect script, included in ${srcdir}/scripts/emake.

This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

‘rebuild’

This target accepts searches out a list of kernel names from the ${DESTDIR}/lib/modules directory and builds rpms for those kernels and for each of a set of architectures given in the AM_RPMTARGETS variable to make. This is convenience target for building a group of rpms on a given build machine.

This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

‘resign’

This target will search out and sign, with a GPG signature, the source rpm, and all of the binary rpms for this package that can be found in the package distribution directory. This target will prompt for a GPG password. Automated or unattended builds can be achieved with the emake expect script located here: ${srcdir}/scripts/emake.

This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

7.7.1.10 Debian Build Targets

On Debian systems, or systems sporting Debian packaging tools, the following targets are used to generate Debian release packages. The release number can be controlled by the contents of the .debrelease file, or with the --with-debrelease=RELEASENUMBER option to configure. See ‘configure --help’ for more information on options.

‘dsc’: This target will build the Debian source change package (.dsc file). We use release number ‘0’ so that the entire tarball is included in the dsc file. You can use release number ‘1’ for the same purposes. Release numbers above ‘1’ will not include the entire tarball. The .dsc file will be named: netperf_2.3.7-0.dsc.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.
‘sigs’: This target signs the .deb files. You will be prompted for a password, unless to specify it to make with the GNUPGPASS variable.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.
‘debs’: This target will build the Debian binary package (.deb file) from the .dsc created above. (This target will also create the .dsc if it has not been created already.) The subpackage .deb files will be named: netperf-*_2.3.7-0_*.deb, where the stars indicate the subpackage and the architecture.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.
‘csig’: This target signs the .dsc file. You will be prompted for a password, unless to specify it to make with the GNUPGPASS variable.
This is an OpenSS7 Project specific makefile target. This target does not require root privilege.

7.7.1.11 Documentation Targets

On systems that have doxygen(1) documentation tool, the following targets are used to generate doxygen html documentation:

‘doxy’: This target generates doxygen(1) documetnation from suitably marked sources. File containing the necessary documentation marks are discovered automatically by configure. Doxygen documentation can be generated bus is not distributed. Documentation is cerated in the subdirectory doc/html.

8 Troubleshooting

8.1 Test Suites

8.1.1 Pre-installation Checks

Most OpenSS7 packages, including the OpenSS7 NETPERF Utility package, ship with pre-installation checks integral to the build system. Pre-installation checks include check scripts that are shipped in the scripts subdirectory as well as specialized make targets that perform the checks.

When building and installing the package from RPM or DEB source packages (see Building from the Source RPM; and Building from the Debian DSC), a fundamental set of post-compile, pre-installation checks are performed prior to building binary packages. This is performed automatically and does not require any special actions on the part of the user creating binary packages from source packages.

When building and installing the package from tarball (see Building from the Tar Ball; and Installing the Tar Ball), however, pre-installation checks are only performed if specifically invoked by the builder of the package. Pre-installation checks are invoked after building the package and before installing the package. Pre-installation checks are performed by invoking the ‘check’ or ‘check.log’ target to make when building the package, as shown in testsuite:ex0.

     % wget http://www.openss7.org/netperf-2.3.7.tar.bz2
     % tar -xjvf netperf-2.3.7.tar.bz2
     % pushd netperf-2.3.7
     % ./configure
     % make
     % make check  # <------- invoke pre-installation checks
     % popd

Example 8.1: Invoking Pre-Installation Checks

Pre-installation checks fall into two categories: System Checks and Maintenance Checks.

8.1.1.1 Pre-Installation System Checks

System Checks are post-compilation checks that can be performed before installing the package that check to ensure that the compiled objects function and will be successfully installed. When the --enable-maintainer-mode option has not been passed to configure, only System Checks will be performed.

For example, the steps shown in testsuite:ex1 will perform System checks.

     % wget http://www.openss7.org/netperf-2.3.7.tar.bz2
     % tar -xjvf netperf-2.3.7.tar.bz2
     % pushd netperf-2.3.7
     % ./configure
     % make
     % make check  # <------ invokes System pre-installation checks
     % popd

Example 8.2: Invoking System Checks

8.1.1.2 Pre-Installation Maintenance Checks

Maintenance Checks include all System Checks, but also checks to ensure that the kernel modules, applications programs, header files, development tools, test programs, documentation, and manual pages conform to OpenSS7 standards. When the --enable-maintainer-mode option has been passed to configure, Maintenance Checks will be performed.

For example, the steps shown in testsuite:ex2 will perform Maintenance checks.

     % wget http://www.openss7.org/netperf-2.3.7.tar.bz2
     % tar -xjvf netperf-2.3.7.tar.bz2
     % pushd netperf-2.3.7
     % ./configure --enable-maintainer-mode
     % make
     % make check  # <------ invokes Maintenance pre-installation checks
     % popd

Example 8.3: Invoking Maintenance Checks

8.1.1.3 Specific Pre-Installation Checks

A number of check scripts are provided in the scripts subdirectory of the distribution that perform both System and Maintenance checks. These are as follows:

check_commands

This check performs both System and Maintenance checks.

When performing System tests, the following tests are performed:

Unless cross-compiling, or unless a program is included in AM_INSTALLCHECK_STD_OPTIONS_EXEMPT every program in bin_PROGRAMS, sbin_PROGRAMS, and libexec_PROGRAMS is tested to ensure that the --help, --version, and --copying options are accepted. When cross-compiling is is not possible to execute cross-compiled binaries, and these checks are skipped in that case.

Script executables, on the other hand, can be executed on the build host, so, unless listed in AM_INSTALLCHECK_STD_OPTIONS_EXEMPT, every program in dist_bit_SCRIPTS, dist_sbin_SCRIPTS, and pkglibexec_SCRIPTS are tested to ensure that the --help, --version, and --copying options are accepted.

When performing Maintenance tests, check_commands also checks to ensure that a manual page exists in section 1 for every executable binary or script that will be installed from bin_PROGRAMS and dist_bin_SCRIPTS. It also checks to ensure that a manual page exists in section 8 for every executable binary or script that will be installed from sbin_PROGRAMS, dist_sbin_SCRIPTS, libexec_PROGRAMS, and pkglibexec_SCRIPTS.

check_decls

This check only performs Maintenance checks.

It collects the results from the check_libs, check_modules and check_headers check scripts and tests to ensure every declaration of a function prototype or external variable contained in installed header files has a corresponding exported symbol from either a to be installed shared object library or a to be installed kernel module. Declarations are exempted from this requirement if their identifiers have been explicitly added to the EXPOSED_SYMBOL variable. If WARN_EXCESS is set to ‘yes’, then the check script will only warn when excess declarations exist (without a corresponding exported symbol); otherwise, the check script will generate an error and the check will fail.

check_headers

This check only performs Maintenance checks.

When performing Maintenance tests, it identifies all of the declarations included in to be installed header files. It then checks to ensure that a manual page exists in sections 2, 3, 7 or 9, as appropriate, for the type of declaration. It also checks to see if a manual page source file exists in the source directory for a declaration that has not been included in the distribution. Function or prototype declarations that do not have a manual page in sections 2, 3, or 9 will cause the check to fail. Other declarations (‘variable’, ‘externvar’, ‘macro’, ‘enumerate’, ‘enum’, ‘struct’, ‘union’, ‘typedef’, ‘member’, etc.) will only warn if a manual page does not exist, but will not fail the check.

check_libs

This check only performs Maintenance checks.

When performing Maintenance tests, it checks that each exported symbol in each to be installed shared object library has a manual page in section 3. It also checks that each exported symbol has a ‘function’, ‘prototype’ or ‘externvar’ declaration in the to be installed header files. A missing declaration or manual page will cause this check to fail.

check_mans

This check only performs Maintenance checks.

When performing Maintenance tests, it checks that to be install manual pages can be formatted for display without any errors or warnings from the build host man program. It also checks that required headings exist for manual pages according to the section in which the manual page will be installed. It warns if recommended headings are not included in the manual pages. Because some RPM distributions have manual pages that might conflict with the package manual pages, this check script also checks for conflicts with installed manual pages on the build host. This check script also checks to ensure that all to be installed manual pages are used in some fashion, that is, they have a declaration, or exported symbol, or are the name of a kernel module or STREAMS module or driver, possibly capitalized.

Note that checking for conflicts with the build host should probably be included in the System checks (because System checks are performed before the source RPM %install scriptlet).

check_modules

This check performs both System and Maintenance checks.

When performing System tests, it checks each to be installed kernel module to ensure that all undefined symbols can be resolved to either the kernel or another module. It also checks whether an exported or externally declared symbol conflicts with an exported or externally declared symbol present in the kernel or another module.³⁴

When performing Maintenance tests, this check script tests that each to be installed kernel module has a manual page in section 9 and that each exported symbol that does not begin with an underscore, and that belongs to an exported function or exported variable, has a manual page in section 9. It also checks to ensure that each exported symbol that does not begin with an underscore, and that belongs to an exported function or exported variable, has a ‘function’, ‘prototype’ or ‘externvar’ declaration in the to be installed header files.

check_streams

This check performs only Maintenance checks.

When performing Maintenance tests, it checks that for each configured STREAMS module or driver, or device node, that a manual page exists in section 4 or section 7 as appropriate.

The output of the pre-installation tests are fairly self explanatory. Each check script saves some output to name.log, where name is the name of the check script as listed above. A summary of the results of the test are display to standard output and can also be captured to the check.log file if the ‘check.log’ target is used instead of the ‘check’ target to make.

Because the check scripts proliferate name.log files throughout the build directory, a ‘make check-clean’ make target has be provided to clean them out. ‘make check-clean’ should be run before each successive run of ‘make check’.

8.1.2 Post-installation Checks

Most OpenSS7 packages ship with a compatibility and conformance test suite built using the ‘autotest’ capabilities of ‘autoconf’. These test suites act as a wrapper for the compatibility and conformance test programs that are shipped with the package.

Unlike the pre-installation checks, the post-installation checks are always run complete. The only check that post-installation test scripts perform is to test whether they have been invoked with root privileges or not. When invoked as root, or as a plain user, some tests might be skipped that require root privileges, or that require plain user privileges, to complete successfully.

8.1.2.1 Running Test Suites

There are several ways of invoking the conformance test suites:

The test suites can be run after installation of the package by invoking the ‘make installcheck’ or ‘make installcheck.log’ target. Some packages require that root privileges be acquired before invoking the package.
The test suites can be run from the distribution subdirectory after installation of the package by invoking the testsuite shell script directly.
The test suites can be run standalone from the libexec (/usr/libexec) installation directory by invoking the testsuite shell script directly.

Typical steps for invoking the test suites directly from make are shown in testsuite:ex3.

     % wget http://www.openss7.org/netperf-2.3.7.tar.bz2
     % tar -xjvf netperf-2.3.7.tar.bz2
     % pushd netperf-2.3.7
     % ./configure
     % make
     % make check  # <------ invokes System pre-installation checks
     % make install
     % sudo make installcheck # <------- invokes post-installation tests
     % popd

Example 8.4: Invoking System Checks

When performing post-installation checks for the purposes of generating a problem report, the checks should always be performed from the build directory, either with ‘make installcheck’ or by invoking testsuite directly from the tests subdirectory of the build directory. This ensures that all of the information known to configure and pertinent to the configuration of the system for which a test case failed, will be collected in the resulting testsuite.log file deposited upon test suite failure in the tests directory. This testsuite.log file can then be attached as part of the problem report and provides rich details to maintainers of the package. See also See Problem Reports, below.

Typical steps for invoking and installed testsuite standalone are shown in testsuite:ex4.

     % [sudo] /usr/libexec/netperf/testsuite

Example 8.5: Invoking testsuite Directly

When invoked directly, testsuite will generate a testsuite.log file in the current directory, and a testsuite.dir directory of failed tests cases and debugging scripts. For generating a problem report for failed test cases, see Stand Alone Problem Reports.

8.2 Problem Reports

8.2.1 Problem Report Guidelines

Problem reports in the following categories should include a log file as indicated in the table below:

‘./configure’: A problem with the configuration process occurs that causes the ‘./configure’ command to fail. The problem report must include the config.log file that was generated by configure.
‘make compile.log’: A problem with the build process occurs that causes the ‘make’ command to fail. Perform ‘make clean’ and then ‘make compile.log’ and attach the config.log and compile.log files to the problem report.
‘make check.log’: A problem occurs with the ‘make check’ target that causes it to fail. Perform ‘make check-clean check.log’ and attach the config.log, compile.log and check.log files to the problem report.
‘sudo make install.log’: A problem occurs with ‘sudo make install’ that causes it to fail. Perform ‘sudo make uninstall’ and ‘sudo make install.log’ and attach the config.log, compile.log, check.log, and install.log files to the problem report.
‘[sudo] make installcheck.log’: A problem occurs with the ‘make installcheck’ target that causes the test suite to fail. Attach the resulting tests/testsuite.log and installcheck.log file to the problem report. There is no need to attach the other files as they are included in tests/testsuite.log.
‘[sudo] make uninstall.log’: A problem occurs with the ‘make uninstall’ target that causes the test suite to fail. Perform ‘sudo make uninstall.log’ and attach the config.log, compile.log, check.log, install.log, installcheck.log, tests/testsuite.log and uninstall.log file to the problem report.
‘[sudo] make remove.log’: A problem occurs with the ‘make remove’ target that causes the test suite to fail. Perform ‘sudo make remove.log’ and attach the config.log, compile.log, check.log, install.log, installcheck.log, tests/testsuite.log and remove.log file to the problem report.

For other problems that occur during the use of the OpenSS7 NETPERF Utility package, please write a test case for the test suite that recreates the problem if one does not yet exist and provide a test program patch with the problem report. Also include whatever log files are generated by the kernel (cmn_err(9)) or by the strerr(8) or strace(1) facilities (strlog(9)).

8.2.2 Generating Problem Reports

The OpenSS7 Project uses the GNU GNATS system for problem reporting. Although the ‘send-pr’ tool from the GNU GNATS package can be used for bug reporting to the project's GNATS database using electronic mail, it is not always convenient to download and install the GNATS system to gain access to the ‘send-pr’ tool.

Therefore, the OpenSS7 NETPERF Utility package provides the ‘send-pr’ shell script that can be used for problem reporting. The ‘send-pr’ shell script can invoked directly and is a work-alike for the GNU ‘send-pr’ tool.

The ‘send-pr’ tool takes the same flags and can be used in the same fashion, however, whereas ‘send-pr’ is an interactive tool³⁵, ‘send-pr’ is also able to perform batch processing. Whereas ‘send-pr’ takes its field information from local databases or from using the ‘query-pr’ C-language program to query a remote database, the ‘send-pr’ tool has the field database internal to the tool.

Problem reports can be generate using make, See Problem Report Targets. An example of how simple it is to generate a problem report is illustrated in autopr:ex0.

     % make pr
     SEND-PR:
     SEND-PR: send-pr:  send-pr was invoked to generate an external report.  An
     SEND-PR: automated problem report has been created in the file named
     SEND-PR: 'problem.pr' in the current directory.  This problem report can
     SEND-PR: be sent to bugs@openss7.org by calling this script as
     SEND-PR: '/home/brian/os7/scripts/send-pr --file="problem.pr"'.
     SEND-PR:
     SEND-PR: It is possible to edit some of the fields before sending on the
     SEND-PR: problem report.  Please remember that there is NO WARRANTY.  See
     SEND-PR: the file 'COPYING' in the top level directory.
     SEND-PR:
     SEND-PR: Please do not send confidential information to the bug report
     SEND-PR: address.  Inspect the file 'problem.pr' for confidential
     SEND-PR: information before mailing.
     SEND-PR:
     % vim problem.pr  # <--- follow instructions at head of file
     % make send-pr

Example 8.6: Invoking Problem Report Generation

Using the ‘make pr’ target to generate a problem report has the advantages that it will assemble any available *.log files in the build directory and attach them to the problem report.

8.2.3 Automatic Problem Reports

The OpenSS7 NETPERF Utility package also provides a feature for automatic problem report generation that meets the problem report submission guidelines detailed in the preceding sections.

Whenever a logging makefile target (see Logging Targets) is invoked, if the primary target fails, the send-pr shell script is invoked to automatically generate a problem report file suitable for the corresponding target (as described above under see Problem Report Guidelines). An example is shown in autopr:ex1.

     % make compile.log
     ...
     ...
     make[5]: *** [libXNSdrvs_a-ip.o] Error 1
     make[5]: Leaving directory `/u6/buildel4/strxns'
     make[4]: *** [all-recursive] Error 1
     make[4]: Leaving directory `/u6/buildel4/strxns'
     make[3]: *** [all] Error 2
     make[3]: Leaving directory `/u6/buildel4/strxns'
     make[2]: *** [all-recursive] Error 1
     make[2]: Leaving directory `/u6/buildel4'
     make[1]: *** [all] Error 2
     make[1]: Leaving directory `/u6/buildel4'
     SEND-PR:
     SEND-PR: send-pr:  Make target compile.log failed in the compile stage.  An
     SEND-PR: automated problem report has been created in the file named
     SEND-PR: 'problem.pr' in the current directory.  This problem report can
     SEND-PR: be sent to bugs@openss7.org by calling 'make send-pr'.
     SEND-PR:
     SEND-PR: It is possible to edit some of the fields before sending on the
     SEND-PR: problem report.  Please remember that there is NO WARRANTY.  See
     SEND-PR: the file 'COPYING' in the top level directory.
     SEND-PR:
     SEND-PR: Please do not send confidential information to the bug report
     SEND-PR: address.  Inspect the file 'problem.pr' for confidential
     SEND-PR: information before mailing.
     SEND-PR:
     % vim problem.pr  # <--- follow instructions at head of file
     % make send-pr

Example 8.7: Problem Report from Failed Logging Target

8.2.4 Stand Alone Problem Reports

The OpenSS7 NETPERF Utility package installs the send-pr script and its configuration file send-pr.config in ${libexecdir}/netperf along with the validation testsuite, see See Test Suites. As with the testsuite, this allows the send-pr script to be used for problem report generation on an installed system that does not have a build directory.

An example of invoking the package testsuite and then generating a problem report for failed cases is shown in autopr:ex2.

     % [sudo] /usr/libexec/netperf/testsuite
     % # test cases failed...
     % /usr/libexec/netperf/send-pr
     SEND-PR:
     SEND-PR: send-pr:  send-pr was invoked to generate an external report.  An
     SEND-PR: automated problem report has been created in the file named
     SEND-PR: 'problem.pr' in the current directory.  This problem report can
     SEND-PR: be sent to bugs@openss7.org by calling this script as
     SEND-PR: '/usr/libexec/netperf/send-pr --file problem.pr'.
     SEND-PR:
     SEND-PR: It is possible to edit some of the fields before sending on the
     SEND-PR: problem report.  Please remember that there is NO WARRANTY.  See
     SEND-PR: the file 'COPYING' in the top level directory.
     SEND-PR:
     SEND-PR: Please do not send confidential information to the bug report
     SEND-PR: address.  Inspect the file 'problem.pr' for confidential
     SEND-PR: information before mailing.
     SEND-PR:
     % vim problem.pr  # <--- follow instructions at head of file
     % /usr/libexec/netperf/send-pr --file problem.pr

Example 8.8: Invoking send-pr Directly

The advantage of the approach shown in the example is that the send-pr script is capable of collecting the testsuite.log file and the failed test cases and debugging scripts from the testsuite.dir directory and including them in the problem report, as well as all package pertinent information from the installed send-pr.config.

8.3 Known Problems

The OpenSS7 Project does not ship software with known bugs. All bugs are unknown.

Verified behaviour is that behaviour that has been verified by conformance test suites that are shipped with the OpenSS7 NETPERF Utility package.

Unverified behaviour may contain unknown bugs.

Please remember that there is NO WARRANTY.

See also Bugs, or file BUGS in the release directory.

Licenses

Hewlett-Packard License

HEWLETT-PACKARD LICENSE

The enclosed software and documentation includes copyrighted works of Hewlett-Package Co. For as long as you comply with the following limitations, you are hereby authorized to (i) use, reproduce, and modify the software and documentation, and to (ii) distribute the software and documentation, including modifications, for non-commercial purposes only.

The enclosed software and documentation is made available at no charge in order to advance the general development of high-performance networking products.
You may not delete any copyright notices contained in the software or documentation. All hard copies, and copies in source code or object code form, of the software or documentation (including modifications) must contain at least one of the copyright notices.
The enclosed software and documentation has not been subjected to testing and quality control and is not a Hewlett-Packard Co. product. At a future time, Hewlett-Packard Co. may or may not offer a version of the software and documentation as a product.
THE SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS". HEWLETT-PACKARD COMPANY DOES NOT WARRANT THAT THE USE, REPRODUCTION, MODIFICATION OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE A THIRD PARTY'S INTELLECTUAL PROPERTY RIGHTS. HP DOES NOT WARRANT THAT THE SOFTWARE OR DOCUMENTATION IS ERROR FREE. HP DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, WITH REGARD TO THE SOFTWARE AND THE DOCUMENTATION. HP SPECIFICALLY DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
HEWLETT-PACKARD COMPANY WILL NOT IN ANY EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS) RELATED TO ANY USE, REPRODUCTION, MODIFICATION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENATION.

GNU Affero General Public License

The GNU Affero General Public License.

Version 3, 19 November 2007

     Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/
     
     Everyone is permitted to copy and distribute verbatim copies of this
     license document, but changing it is not allowed.

Preamble

The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program–to make sure it remains free software for all its users.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.

A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.

The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.

An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS

Definitions.
“This License” refers to version 3 of the GNU Affero General Public License.
“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
A “covered work” means either the unmodified Program or a work based on the Program.
To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
Source Code.
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
Basic Permissions.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
1. The work must carry prominent notices stating that you modified it, and giving a relevant date.
2. The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
3. You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
4. If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
1. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
2. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
3. Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
4. Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
5. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
Additional Terms.
“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
1. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
2. Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
3. Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
4. Limiting the use for publicity purposes of names of licensors or authors of the material; or
5. Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
6. Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
Termination.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
Patents.
A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.
A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
Remote Network Interaction; Use with the GNU General Public License.
Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.

     one line to give the program's name and a brief idea of what it does.
     Copyright (C) year name of author
     
     This program is free software: you can redistribute it and/or modify
     it under the terms of the GNU Affero General Public License as published by
     the Free Software Foundation, either version 3 of the License, or (at
     your option) any later version.
     
     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
     Affero General Public License for more details.
     
     You should have received a copy of the GNU Affero General Public License
     along with this program.  If not, see http://www.gnu.org/licenses/.

Also add information on how to contact you by electronic and paper mail.

If your software can interact with users remotely through a network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a “Source” link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.

You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see http://www.gnu.org/licenses/.

GNU General Public License

GNU GENERAL PUBLIC LICENSE

Version 3, 29 June 2007

     Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/
     
     Everyone is permitted to copy and distribute verbatim copies of this
     license document, but changing it is not allowed.

Preamble

The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program–to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS

Definitions.
“This License” refers to version 3 of the GNU General Public License.
“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
A “covered work” means either the unmodified Program or a work based on the Program.
To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
Source Code.
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
Basic Permissions.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
1. The work must carry prominent notices stating that you modified it, and giving a relevant date.
2. The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
3. You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
4. If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
1. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
2. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
3. Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
4. Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
5. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
Additional Terms.
“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
1. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
2. Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
3. Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
4. Limiting the use for publicity purposes of names of licensors or authors of the material; or
5. Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
6. Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
Termination.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
Patents.
A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.
A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

     one line to give the program's name and a brief idea of what it does.
     Copyright (C) year name of author
     
     This program is free software: you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
     the Free Software Foundation, either version 3 of the License, or (at
     your option) any later version.
     
     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.
     
     You should have received a copy of the GNU General Public License
     along with this program.  If not, see http://www.gnu.org/licenses/.

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

     program Copyright (C) year name of author
     This program comes with ABSOLUTELY NO WARRANTY; for details type ‘show w’.
     This is free software, and you are welcome to redistribute it
     under certain conditions; type ‘show c’ for details.

The hypothetical commands ‘show w’ and ‘show c’ should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.

The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read http://www.gnu.org/philosophy/why-not-lgpl.html.

GNU Lesser General Public License

GNU LESSER GENERAL PUBLIC LICENSE

Version 3, 29 June 2007

     Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/
     
     Everyone is permitted to copy and distribute verbatim copies of this
     license document, but changing it is not allowed.

TERMS AND CONDITIONS

This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.

Additional Definitions.
As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
1. under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
2. under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
1. Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
2. Accompany the object code with a copy of the GNU GPL and this license document.
Combined Works.
You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
1. Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
2. Accompany the Combined Work with a copy of the GNU GPL and this license document.
3. For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
4. Do one of the following:
  1. Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
  2. Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
5. Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
Combined Libraries.
You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
1. Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
2. Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.

END OF TERMS AND CONDITIONS

GNU Free Documentation License

GNU FREE DOCUMENTATION LICENSE

Version 1.1, March 2000

     Copyright © 2000 Free Software Foundation, Inc.
     59 Temple Place, Suite 330, Boston, MA  02111-1307, USA
     
     Everyone is permitted to copy and distribute verbatim copies
     of this license document, but changing it is not allowed.

PREAMBLE

The purpose of this License is to make a manual, textbook, or other written document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The “Document”, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as “you”.
A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License.
The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.
A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not “Transparent” is called “Opaque”.
Examples of suitable formats for Transparent copies include plain ascii without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only.
The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
VERBATIM COPYING
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
COPYING IN QUANTITY
If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
MODIFICATIONS
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five).
3. State on the Title page the name of the publisher of the Modified Version, as the publisher.
4. Preserve all the copyright notices of the Document.
5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
8. Include an unaltered copy of this License.
9. Preserve the section entitled “History”, and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled “History” in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
11. In any section entitled “Acknowledgments” or “Dedications”, preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgments and/or dedications given therein.
12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
13. Delete any section entitled “Endorsements”. Such a section may not be included in the Modified Version.
14. Do not retitle any existing section as “Endorsements” or to conflict in title with any Invariant Section.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
COMBINING DOCUMENTS
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections entitled “History” in the various original documents, forming one section entitled “History”; likewise combine any sections entitled “Acknowledgments”, and any sections entitled “Dedications”. You must delete all sections entitled “Endorsements.”
COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an “aggregate”, and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate.
TRANSLATION
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail.
TERMINATION
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

END OF TERMS AND CONDITIONS

ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

       Copyright (C)  year  your name.
       Permission is granted to copy, distribute and/or modify this document
       under the terms of the GNU Free Documentation License, Version 1.1
       or any later version published by the Free Software Foundation;
       with the Invariant Sections being list their titles, with the
       Front-Cover Texts being list, and with the Back-Cover Texts being list.
       A copy of the license is included in the section entitled ``GNU
       Free Documentation License''.

If you have no Invariant Sections, write “with no Invariant Sections” instead of saying which ones are invariant. If you have no Front-Cover Texts, write “no Front-Cover Texts” instead of “Front-Cover Texts being list”; likewise for Back-Cover Texts.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.

Indices

Index of Concepts

apt: Downloading with APT
apt: Repositories for APT
Architectures: Linux Architectures
authors: Authors
binary debs: Removing the Debian DEB
binary debs: Installing the Debian DEB
binary debs: Configuring the Debian DEB
binary debs: Downloading the Debian DEB
binary rpms: Removing the Binary RPM
binary rpms: Installing the Binary RPM
binary rpms: Configuring the Binary RPM
binary rpms: Downloading the Binary RPM
bug reports, automatic generation: Automatic Problem Reports
bug reports, generating: Generating Problem Reports
bug reports, stand along generation: Stand Alone Problem Reports
bugs: Bugs
bugs, history: Historical Defects
bugs, known: Known Defects
bugs, reporting: Problem Reports
building: Building
building, source dscs: Building from the Debian DSC
building, source srpm: Building from the Source RPM
building, tar ball: Building from the Tar Ball
checkout, cvs: Downloading from CVS
compatibility: Compatibility
configuration: Configuration
configure environment variables: Environment Variables
configure options: Configure Options
configuring, binary debs: Configuring the Debian DEB
configuring, binary rpms: Configuring the Binary RPM
configuring, source dscs: Configuring the Debian DSC
configuring, source srpm: Configuring the Source RPM
configuring, tar ball: Configuring the Tar Ball
conformance: Conformance
contributors: Contributors
conventions: Conventions
cpu utilization: CPU Utilization
credits: Acknowledgements
cvs: Downloading from CVS
definitions: Conventions
design: Design
design basics: Design Basics
developing: Development
downloading: Downloading
downloading, apt: Downloading with APT
downloading, binary rpms: Downloading the Binary RPM
downloading, debian debs: Downloading the Debian DEB
downloading, debian dscs: Downloading the Debian DSC
downloading, source srpm: Downloading the Source RPM
downloading, tar ball: Downloading the Tar Ball
downloading, yum: Downloading with YUM
drivers: Drivers
generating bug reports: Stand Alone Problem Reports
generating bug reports: Generating Problem Reports
generating bug reports automatically: Automatic Problem Reports
generating problem reports: Generating Problem Reports
generating problem reports automatically: Automatic Problem Reports
generating problem reports stand alone: Stand Alone Problem Reports
GNU/Linux Distributions: GNU/Linux Distributions
headers: Files
history: History
history bugs: Historical Defects
HP Netperf: HP Netperf
indices: Indices
installation: Installation
installing: Installing
installing, binary debs: Installing the Debian DEB
installing, binary rpms: Installing the Binary RPM
installing, tar ball: Installing the Tar Ball
interfaces supported: Supported Interfaces
introduction: Introduction
Kernel: Linux Kernel
known bugs: Known Defects
known problems: Known Problems
libraries: Libraries
license, AGPL: GNU Affero General Public License
license, FDL: GNU Free Documentation License
license, GNU Affero General Public License: GNU Affero General Public License
license, GNU Free Documentation License: GNU Free Documentation License
license, GNU General Public License: GNU General Public License
license, GPL: GNU General Public License
license, Hewlett-Packard: Hewlett-Packard License
license, HP: Hewlett-Packard License
license, Lesser General Public License: GNU Lesser General Public License
license, LGPL: GNU Lesser General Public License
licenses: Licenses
licensing: Notice
Linux Fast-STREAMS: Linux Fast-STREAMS
Linux STREAMS: Linux STREAMS
maintainer: Maintainer
manual abstract: Abstract
manual audience: Abstract
manual disclaimer: Disclaimer
manual intent: Abstract
manual notice: Notice
manual objective: Abstract
manual revisions: Revisions
maturity: Maturity
modules: Modules
netperf-dev-2.3.7-1.7.2.i686.rpm: Configuring the Binary RPM
netperf-devel-2.3.7-1.7.2.i686.rpm: Configuring the Binary RPM
netperf-doc-2.3.7-1.7.2.i686.rpm: Configuring the Binary RPM
netperf-LiS-lib-2.3.7-1.7.2.i686.rpm: Configuring the Binary RPM
netperf-LiS-util-2.3.7-1.7.2.i686.rpm: Configuring the Binary RPM
netperf-source-2.3.7-1.7.2.i686.rpm: Configuring the Binary RPM
netperf-streams-lib-2.3.7-1.7.2.i686.rpm: Configuring the Binary RPM
netperf-streams-util-2.3.7-1.7.2.i686.rpm: Configuring the Binary RPM
objective: Objective
Options Test Global: Global Options
Options Test Specific: Test Options
organization: Organization
overview: Overview
post-installation checks: Post-installation Checks
pre-installation checks: Pre-installation Checks
prerequisites: Prerequisites
problem reports: Problem Reports
problems, known: Known Problems
protocols supported: Supported Protocols
quick start guide: Quick Start Guide
reference: Reference
release netperf-2.3.1: Release netperf-2.3.1
release netperf-2.3.2: Release netperf-2.3.2
release netperf-2.3.3: Release netperf-2.3.3
release netperf-2.3.4: Release netperf-2.3.4
release netperf-2.3.4.rc2: Release netperf-2.3.4.rc2
release netperf-2.3.4.rc3: Release netperf-2.3.4.rc3
release netperf-2.3.4rc1: Release netperf-2.3.4rc1
release netperf-2.3.5: Release netperf-2.3.5
release netperf-2.3.6: Release netperf-2.3.6
release netperf-2.3.7: Release netperf-2.3.7
release notes: Release Notes
releases: Releases
removing: Removing
removing, binary debs: Removing the Debian DEB
removing, binary rpms: Removing the Binary RPM
removing, source dscs: Removing the Debian DSC
removing, source srpm: Removing the Source RPM
removing, tar ball: Removing the Tar Ball
reporting bugs: Problem Reports
repositories: Repositories
repositories, apt: Repositories for APT
repositories, yum: Repositories for YUM
schedule: Schedule
source dscs: Removing the Debian DSC
source dscs: Building from the Debian DSC
source dscs: Configuring the Debian DSC
source dscs: Downloading the Debian DSC
source rpms: Removing the Source RPM
source rpms: Building from the Source RPM
source rpms: Configuring the Source RPM
source rpms: Downloading the Source RPM
sponsors: Sponsors
supported interfaces: Supported Interfaces
supported protocols: Supported Protocols
supported tests: Supported Tests
tar ball: Removing the Tar Ball
tar ball: Installing the Tar Ball
tar ball: Building from the Tar Ball
tar ball: Configuring the Tar Ball
tar ball: Downloading the Tar Ball
test suites: Test Suites
test suites, running: Running Test Suites
tests: Tests
Tests Connect/Close: CC
Tests Connect/Close SCTP Sockets: SCTP_CC
Tests Connect/Close TCP Sockets: TCP_CC
tests performance bulk data transfer: Using Netperf to measure bulk data transfer performance
tests performance bulk data transfer: Available bulk data transfer performance tests
Tests Request/Response: Request/Response Tests
Tests Request/Response ATM FORE: FORE_RR
Tests Request/Response Blocking: RR
Tests Request/Response CL DLPI: DLCL_RR
Tests Request/Response CL UNIX LWP Sockets: LWPDG_RR
Tests Request/Response CL UNIX Sockets: DG_RR
Tests Request/Response CO DLPI: DLCO_RR
Tests Request/Response CO UNIX LWP Sockets: LWPSTR_RR
Tests Request/Response CO UNIX Sockets: STREAM_RR
Tests Request/Response Connect: CRR
Tests Request/Response Connect SCTP Sockets: SCTP_CRR
Tests Request/Response Connect TCP Sockets: TCP_CRR
Tests Request/Response Description: Request/Response Description
Tests Request/Response Non-Blocking: NBRR
Tests Request/Response Non-Blocking SCTP Sockets: SCTP_NBRR
Tests Request/Response Non-Blocking TCP Sockets: TCP_NBRR
Tests Request/Response Performance: Request/Response Performance
Tests Request/Response SCTP IPv6 Sockets: SCTPIPV6_RR
Tests Request/Response SCTP Sockets: SCTP_RR
Tests Request/Response SCTP XTI: XTI_SCTP_RR
Tests Request/Response TCP IPv6 Sockets: TCPIPV6_RR
Tests Request/Response TCP Sockets: TCP_RR
Tests Request/Response TCP XTI: XTI_TCP_RR
Tests Request/Response Transaction: TRR
Tests Request/Response Transaction SCTP Sockets: SCTP_TRR
Tests Request/Response Transaction TCP Sockets: TCP_TRR
Tests Request/Response UDP IPv6 Sockets: UDPIPV6_RR
Tests Request/Response UDP Sockets: UDP_RR
Tests Request/Response UDP XTI: XTI_UDP_RR
Tests Stream: Stream Tests
Tests Stream ATM FORE: FORE_STREAM
Tests Stream CL DLPI: DLCL_STREAM
Tests Stream CL UNIX Sockets: DG_STREAM
Tests Stream CO DLPI: DLCO_STREAM
Tests Stream CO UNIX Sockets: STREAM_STREAM
Tests Stream SCTP Sockets Forward: SCTP_STREAM
Tests Stream SCTP Sockets IPv6 Forward: SCTPIPV6_STREAM
Tests Stream SCTP Sockets Reverse: SCTP_MAERTS
Tests Stream SCTP Sockets Sendfile: SCTP_SENDFILE
Tests Stream SCTP XTI: XTI_SCTP_STREAM
Tests Stream TCP Sockets Forward: TCP_STREAM
Tests Stream TCP Sockets IPv6 Forward: TCPIPV6_STREAM
Tests Stream TCP Sockets Reverse: TCP_MAERTS
Tests Stream TCP Sockets Sendfile: TCP_SENDFILE
Tests Stream TCP XTI: XTI_TCP_STREAM
Tests Stream UDP Sockets: UDP_STREAM
Tests Stream UDP Sockets IPv6 Forward: UDPIPV6_STREAM
Tests Stream UDP XTI: XTI_UDP_STREAM
tests supported: Supported Tests
troubleshooting: Troubleshooting
utilities: Utilities
web resources: Web Resources
yum: Downloading with YUM
yum: Repositories for YUM

Index of Functions and Macros

Index of Variables and Constants

AUTOM4TE: Environment Variables
AUTOTEST: Environment Variables
BZIP2: Environment Variables
BZIP2_CMD: Environment Variables
CHKCONFIG: Environment Variables
DEB_BUILD_ARCH: Environment Variables
DEB_BUILD_GNU_CPU: Environment Variables
DEB_BUILD_GNU_SYSTEM: Environment Variables
DEB_BUILD_GNU_TYPE: Environment Variables
DEB_HOST_ARCH: Environment Variables
DEB_HOST_GNU_CPU: Environment Variables
DEB_HOST_GNU_SYSTEM: Environment Variables
DEB_HOST_GNU_TYPE: Environment Variables
DEPMOD: Environment Variables
DESTDIR: Environment Variables
DPKG: Environment Variables
DPKG_BUILDPACKAGE: Environment Variables
DPKG_SOURCE: Environment Variables
GENKSYMS: Environment Variables
GNUPGHOME: Environment Variables
GNUPGUSER: Environment Variables
GPG: Environment Variables
GPGPASSWD: Environment Variables
GZIP: Environment Variables
GZIP_CMD: Environment Variables
KGENKSYMS: Environment Variables
LDCONFIG: Environment Variables
LSMOD: Environment Variables
LSOF: Environment Variables
MAKEWHATIS: Environment Variables
MODPOST_CACHE: Environment Variables
MODPROBE: Environment Variables
NM: Environment Variables
OBJDUMP: Environment Variables
PACKAGE_KVERSION: Configuring the Source RPM
PIC: Environment Variables
REFER: Environment Variables
RPM: Environment Variables
RPMBUILD: Environment Variables
SOELIM: Environment Variables
TBL: Environment Variables

Index of Tests

DG_RR: DG_RR
DG_STREAM: DG_STREAM
DLCL_RR: DLCL_RR
DLCL_STREAM: DLCL_STREAM
DLCL_STREAM: Available bulk data transfer performance tests
DLCO_RR: DLCO_RR
DLCO_STREAM: DLCO_STREAM
DLCO_STREAM: Available bulk data transfer performance tests
FORE_RR: FORE_RR
FORE_STREAM: FORE_STREAM
FORE_STREAM: Available bulk data transfer performance tests
LWPDG_RR: LWPDG_RR
LWPSTR_RR: LWPSTR_RR
SCTP_CC: SCTP_CC
SCTP_CRR: SCTP_CRR
SCTP_MAERTS: SCTP_MAERTS
SCTP_NBRR: SCTP_NBRR
SCTP_PACKET: Available bulk data transfer performance tests
SCTP_RR: SCTP_RR
SCTP_SENDFILE: SCTP_SENDFILE
SCTP_STREAM: SCTP_STREAM
SCTP_STREAM: Available bulk data transfer performance tests
SCTP_TRR: SCTP_TRR
SCTPIPV6_PACKET: Available bulk data transfer performance tests
SCTPIPV6_RR: SCTPIPV6_RR
SCTPIPV6_STREAM: SCTPIPV6_STREAM
SCTPIPV6_STREAM: Available bulk data transfer performance tests
STREAM_RR: STREAM_RR
STREAM_STREAM: STREAM_STREAM
STREAM_STREAM: Available bulk data transfer performance tests
TCP_CC: TCP_CC
TCP_CRR: TCP_CRR
TCP_MAERTS: TCP_MAERTS
TCP_NBRR: TCP_NBRR
TCP_RR: TCP_RR
TCP_SENDFILE: TCP_SENDFILE
TCP_STREAM: TCP_STREAM
TCP_STREAM: Available bulk data transfer performance tests
TCP_TRR: TCP_TRR
TCPIPV6_RR: TCPIPV6_RR
TCPIPV6_STREAM: TCPIPV6_STREAM
TCPIPV6_STREAM: Available bulk data transfer performance tests
UDP_RR: UDP_RR
UDP_STREAM: UDP_STREAM
UDP_STREAM: Available bulk data transfer performance tests
UDPIPV6_RR: UDPIPV6_RR
UDPIPV6_STREAM: UDPIPV6_STREAM
UDPIPV6_STREAM: Available bulk data transfer performance tests
XTI_SCTP_RR: XTI_SCTP_RR
XTI_SCTP_STREAM: XTI_SCTP_STREAM
XTI_TCP_RR: XTI_TCP_RR
XTI_TCP_STREAM: XTI_TCP_STREAM
XTI_UDP_RR: XTI_UDP_RR
XTI_UDP_STREAM: XTI_UDP_STREAM

Index of Files and Programs

Short Contents

OpenSS7 NETPERF Utility Installation and Reference Manual
About This Manual
Preface
Quick Start Guide
1 Introduction
2 Objective
3 Reference
4 Tests
5 Conformance
6 Releases
7 Installation
8 Troubleshooting
Licenses
Indices

OpenSS7 NETPERF Utility Installation and Reference Manual
About This Manual
Preface
Quick Start Guide
- OpenSS7 NETPERF Utility
1 Introduction
2 Objective
3 Reference
4 Tests
5 Conformance
6 Releases
7 Installation
8 Troubleshooting
Licenses
Indices

Footnotes

[1] http://www.openss7.org/tarballs/netperf-2.3.7.tar.bz2

[2] See GNU/Linux Distributions, for more information.

[3] If you are using a Debian release, please make sure to install the groff extension package (‘groff_ext’), as it contains the refer or grefer commands necessary for including references in the manual pages.

[4] Although, at one time, this package supported LiS, LiS is now deprecated and unsupported.

[5] Please see Problem Reports, or the file PROBLEMS in the release directory for more information on filing a proper Problem Report.

[6] Note that macro and reference databse files are not installed if the package is configured for cooked manpages.

[7] Linux STREAMS is buggy, unsupported and deprecated. Do not use it.

[8] Linux STREAMS is buggy, unsupported and deprecated. Do not use it.

[9] Linux STREAMS is buggy, unsupported and deprecated. Do not use it.

[10] See GNU/Linux Distributions, for more information.

[11] If you are using a Debian release, please make sure to install the groff extension package (‘groff_ext’), as it contains the refer or grefer commands necessary for including references in the manual pages.

[12] Although, at one time, this package supported LiS, LiS is now deprecated and unsupported.

[13] Items marked as ‘TBD’ are scheduled to have support deprecated. That is, in a future release, the distributions marked ‘TBD’ will not longer be validated before release.

[14] At a later date, it is possible to move this package into the kernel, however, with continued resistance to STREAMS from within the Linux developer community, this is currently unlikely.

[15] Linux STREAMS is buggy, unsupported and deprecated. Do not use it.

[16] See sections Disclaimer of Warranty and Limitation of Liability under GNU Affero General Public License.

[17] Not all distributions support the ‘%dev’ RPM macro: a case in point is the SuSE 8.0 distribution which uses an older version of rpm(1). Distributions that do not support the ‘%dev’ macro will build devices as a ‘%post’ operation. Note also that not all release packages contain devices. Only packages that provide STREAMS character device drivers need devices, and then only when the ‘specfs’ or ‘devfsd’ is not being used.

[18] Note that not all releases have source RPM packages. Release packages that do not contain kernel modules do not generate a source RPM package.

[19] Note that not all release packages contain shared libraries, and, therefore, not all release packages contain this package.

[20] Note that not all release packages contain devices. Only packages that provide STREAMS character device drivers need devices, and then only when the ‘specfs’ or ‘devfsd’ is not being used.

[21] Note that not all releases have source DEB packages. Release packages that do not contain kernel modules do not generate a source DEB package.

[22] Note that not all release packages contain shared libraries, and, therefore, not all release packages contain this package.

[23] Older version of bison (2.0) and the older version of flex (2.5.4a) are also suitable. Where possible, use the more recent bison 2.3 and flex 2.5.33.

[24] A notable exception is Debian and Fedora 7. Note that on Fedora 7 the gettext-devel package must be installed.

[25] In particular, for CentOS, Fedora 6 or 7, the tetex-latex and gnuplot packages must be loaded as well. Note also that the latex2html used to be part of the textex package (or subpackages) but is now often packaged on its own. Recent distributions such as SUSE 11.0 and Fedora 9 use the texlive package instead of the tetex package.

[26] In particular, some Debian systems do not load the groff(1) extensions package and do not have grefer(1) installed. Although this is an oversight on the configuration of the particular Debian system, we accomodate such misconfiguration with this feature.

[27] In particular, some Debian or Ubuntu systems do not load the groff(1) extensions package and do not have grefer(1) installed. Although this is an oversight on the configuration of the particular Debian or Ubuntu system, we accomodate such misconfiguration with this feature.

[28] Because it is a cross-build, the kernel version on the build machine is unlikely to be the kernel version of the target machine, except by coincidence.

[29] /usr/libexec/netperf is just an example, the actual location is ${libexecdir}/${PACKAGE}, which varies from distribution to distribution (as some distributions such as Mandriva do not have a libexec directory).

[30] Therefore, it is possible to download the package, configure it, and then uninstall it. This is handy if you do not have the sources used to build and install the package immediately available.

[31] This is useful from the OpenSS7 Master Package.

[32] Theoretically this is true, however, the OpenSS7 Project does not use any maintainer programs that are not generally available (i.e. open source).

[33] Note that because logging targets invoke a pipe, automake(1) does not return the correct return status (always returns success if the tee(1) operation is successful). Therefore, these targets should not be invoked by scripts that need to use the return value from automake(1).

[34] This particular check has caught some name space pollution that has occurred in the 2.6.11 kernel.

[35] ‘send-pr’ launches the user's EDITOR to edit the problem report before submitting it.

netperf Manual

Description: OpenSS7 Online Manuals

OpenSS7 NETPERF Utility

OpenSS7 NETPERF Utility Installation and Reference Manual

About This Manual

Preface

Notice

Abstract

Objective

Intent

Audience

Revisions

Version Control

ISO 9000 Compliance

Disclaimer

U.S. Government Restricted Rights

Acknowledgements

Sponsors

Contributors

Authors

Maintainer

Web Resources

Bug Reports

Mailing Lists

Spam

Acceptable Use Policy

Large Attachments

Quick Start Guide

OpenSS7 NETPERF Utility

Release

Prerequisites

Installation

Brief Installation Instructions

Detailed Installation Instructions

1 Introduction

1.1 Overview

1.2 Organization of this Manual

1.3 Conventions and Definitions

2 Objective

3 Reference

3.1 Files

3.2 Drivers

3.3 Modules

3.4 Libraries

3.5 Utilities

3.6 Development

4 Tests

4.1 Design

4.1.1 Design Basics

4.1.2 CPU Utilization

4.1.3 Supported Interfaces

4.1.4 Supported Protocols

4.1.5 Supported Tests

4.2 Stream Tests

4.2.1 Available bulk data transfer performance tests

4.2.1.1 Forward Unidirectional Stream Performance Test (STREAM)

4.2.1.2 Reverse Unidirectional Stream Performance Test (MAERTS)

4.2.1.3 Paged Unidirectional Stream Performance Test (SENDFILE)

4.2.2 Using Netperf to measure bulk data transfer performance

4.2.2.1 SCTP Stream Forward Performance

4.2.2.2 SCTP Stream Reverse Performance

4.2.2.3 SCTP Stream Sendfile Performance

4.2.2.4 TCP Stream Forward Performance

4.2.2.5 TCP Stream Reverse Performance

4.2.2.6 TCP Stream Sendfile Performance

4.2.2.7 UDP Stream Performance

4.2.2.8 XTI SCTP Stream Performance

4.2.2.9 XTI TCP Stream Performance

4.2.2.10 XTI UDP Performance

4.2.2.11 SCTP IPv6 Stream Forward Performance

4.2.2.12 TCP IPv6 Stream Forward Performance

4.2.2.13 UDP IPv6 Stream Forward Performance

4.2.2.14 DLPI Connection Oriented Stream Performance

4.2.2.15 DLPI Connectionless Stream Performance

4.2.2.16 Unix Domain Stream Sockets Performance

4.2.2.17 Unix Domain Datagram Sockets Performance

4.2.2.18 Fore ATM API Stream Performance

4.3 Request/Response Tests

4.3.1 Available request/response performance tests

4.3.1.1 Request/Response Performance Test (RR)