Bay Networks 5390, Administering, Page: 777 / 888

893-741-B C4-5
Utilities
For more details on installing erpcd, see 1) Setting Up the File Server on page A14-2, and 2)
Installation Notes for Annex 10.1 UNIX.
For more details on using the acp_userinfo file, see Creating the acp_userinfo File on page A15-16.
CAUTION:
For expert C coders only: the host erpcd daemon can
implement macros, extended commands, command logging, and arbi-
trary security restrictions through a set of interface routines to the
Model 5390 CLI. These are documented in the acp_policy.doc file; the
acp_policy.c file contains examples (for more details on implementing
code changes, see Modifying the Supplied Security Application on page
A15-74 and Modifying the Code on page A15-84).
Table C4-2. Supported Arguments for erpcd
Argument Description
–D Restarts erpcd in test mode on the load server host – it does
not detach from the tty and it prints out extensive debugging
information. Entering a debugging level increases the amount
of debugging information. Note that there is no space between
the –D and the level number.
–c Specifies the maximum number of child processes that erpcd
can create (so that it can handle simultaneous requests).
–d Specifies a UDP port number; the default is 121.
–f Specifies the location of the bfs files (load/dump); defaults to
the defined bfs directory (usually /usr/spool/erpcd/bfs).
–p Prints the daemon’s process ID to standard output so that
automatic mechanisms can start/stop this process.
–s Specifies the location of the security files (acp_* and
eservices); defaults to the defined install-annex directory
(usually /etc).