spray(8) [opendarwin man page]

SPRAY(8)						    BSD System Manager's Manual 						  SPRAY(8)

NAME

     spray -- send many packets to host

SYNOPSIS

     spray [-c count] [-d delay] [-l length] host ...

DESCRIPTION

     Spray sends multiple RPC packets to host and records how many of them were correctly received and how long it took.

     The options are as follows:

     -c count
	     Send count packets.

     -d delay
	     Pause delay microseconds between sending each packet.

     -l length
	     Set the length of the packet that holds the RPC call message to length bytes.  Not all values of length are possible because RPC data
	     is encoded using XDR.  Spray rounds up to the nearest possible value.

     Spray is intended for use in network testing, measurement, and management.  This command can be very hard on a network and should be used
     with caution.

SEE ALSO

     netstat(1), ifconfig(8), ping(8), rpc.sprayd(8)

BSD
								   July 10, 1995							       BSD

sprayd(1M)																sprayd(1M)

NAME

       rpc.sprayd, sprayd - spray server

SYNOPSIS

       log_file]

DESCRIPTION

       is an RPC server that records the packets sent by from another system (see spray(1M)).

       daemon  may  be started by or through the command line.	The service provided by is not useful as a networking benchmark as it uses unreli-
       able connectionless transports, UDP, for example.  It can report a large number of packets dropped when the drops were caused by  the  pro-
       gram sending packets faster than they can be buffered locally, that is, before the packets get to the network medium.

   Options
       recognizes the following options and command-line arguments:

	      Log any errors to the named log file,
			   log_file.  Errors are not logged if the option is not specified.

			   Information logged to the file includes date and time of the error, host name, process id and name of the function gen-
			   erating the error, and the error message.  Note that different services can share a single log file since enough infor-
			   mation is included to uniquely identify each error.

	      Exit after serving each RPC request.
			   Using the option, the security file can control access to RPC services.

	      Exit only if

			   o  dies (see rpcbind(1M)),
			   o  Another registers with or
			   o  becomes unregistered with

       The option is more efficient because a new process is not launched for each RPC request.  is the default.

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       inetd(1M), rpcbind(1M), spray(1M), inetd.conf(4), inetd.sec(4), services(4).

																	sprayd(1M)