xref: /titanic_50/usr/src/man/man1m/rpc.sprayd.1m (revision ee63a9c96aceb3724cf0ee9b2e586b0dce3908a2)
te
Copyright 1989 AT&T Copyright (c) 2004 Sun Microsystems, Inc. - All Rights Reserved.
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
RPC.SPRAYD 1M "Nov 4, 2004"
NAME
rpc.sprayd, sprayd - spray server
SYNOPSIS

/usr/lib/netsvc/spray/rpc.sprayd
DESCRIPTION

rpc.sprayd is a server that records the packets sent by spray(1M). The rpc.sprayd daemon may be started by inetd(1M) or listen(1M).

The service provided by rpc.sprayd is not useful as a networking benchmark as it uses unreliable connectionless transports, (udp for example). It can report a large number of packets dropped when the drops were caused by the program sending packets faster than they can be buffered locally (before the packets get to the network medium).

SEE ALSO

svcs(1), inetadm(1M), inetd(1M) listen(1M), pmadm(1M), sacadm(1M), spray(1M), svcadm(1M), attributes(5), smf(5)

NOTES

The rpc.sprayd service is managed by the service management facility, smf(5), under the service identifier:

svc:/network/rpc/spray:default

Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). Responsibility for initiating and restarting this service is delegated to inetd(1M). Use inetadm(1M) to make configuration changes and to view configuration information for this service. The service's status can be queried using the svcs(1) command.