ERPCD(8) UNIX System V(ANNEX) ERPCD(8)
NAME
erpcd - Annex network services daemon
SYNOPSIS
/etc/erpcd [ -d [ udpport ] ] [ -D[level] ]
DESCRIPTION
erpcd is the Annex network services daemon. It is normally started at
boot time from the rc(8) file.
The erpcd daemon is responsible for two services: the block file server
used by the Annex to access host files, bfs, and the Annex access control
protocol server that handles security requests, acp. In both cases,
erpcd listens at a well-known UDP port (name "erpc", 121/udp) for
messages indicating a request for services from an Annex. It
authenticates these messages and then reads the file /etc/eservices to
determine what types of requests to service and which server to execute.
Although the well-known port can be specified with the -d number, the
default as specified in /etc/eservices should be used. The -d option
used without the port number argument turns on socket level debugging.
Note that there is a space between the -d and the number. The -D option
puts erpcd in a debug mode where it does not detach from the invokers tty
and instead prints out extensive debugging information. The amount of
debugging information can be increased by giving a debugging level with
the -D option. Note that there is no space between the -D and the
number.
The bfs service is used by the Annex to down-load various host files from
a server host and to up-load crash dump images to a server host. All such
files are resident in /usr/spool/erpcd/bfs or its subdirectories. The
dump file is named by prefixing "dump." to the Internet address of the
Annex. The dump file names are unique for each Annex but not for each
crash dump. An existing dump file is overwritten if the same Annex
crashes again. A dump file is slightly larger than the amount of memory
in the Annex.
When the Annex boots, it uses the bfs service to request three files.
First, the boot rom obtains the Annex operational code that is loaded
into Annex main memory. As part of its booting procedure, the Annex
operational code requests the files gateways and rotaries. The Annex
first requests this file from the host whose address is specified by the
na parameter prefloadaddr. If this host does not respond, the Annex
broadcasts the request. An empty or missing gateways or rotaries file
simply means there is no configuration in that area. It is preferable to
use an empty file rather than not having the file exist, as the Annex
will find the empty file and thus won't have to wait for its open request
to timeout. The gateways file is described in gateways(5). The rotaries
file is described in rotaries(5).
10/89 Page 1
ERPCD(8) UNIX System V(ANNEX) ERPCD(8)
The acp service is used by the Annex to implement host based security
policies that govern Annex operations. See the Annex Network
Administrator's Guide for more information on the acp service.
NOTES
The dump subdirectories should be carefully monitored and any crash dumps
should be sent to your service representative.
FILES
/usr/spool/erpcd/bfs/dump.* crash dumps
/usr/spool/erpcd/bfs/annex.* Annex images
/usr/spool/erpcd/bfs/oper.* Annex images
/usr/spool/erpcd/bfs/gateways
/usr/spool/erpcd/bfs/rotaries
/etc/eservices
SEE ALSO
eservices(5), gateways(5), na(8), rc(8),
routed(8C), rotaries(5).
Annex Network Administrator's Guide.
BUGS
If the gateways or rotaries files are not present on any host, the Annex
may take up to an extra minute to complete its booting procedures.
The -d option takes a space before number; the -D option does not.
Page 2 10/89