Table C-36. Supported Arguments For Erpcd - Bay Networks 6300 Supplement Manual

Supplement to the remote annex administrator’s guide for unix
Hide thumbs Also See for 6300:
Table of Contents

Advertisement

Chapter 4
Utilities
Remote Annex 6300 Supplement to the Remote Annex Administrator's Guide for UNIX
C-116
When operational code is downloaded to Annexes, a minimum of one
host, accessible to an Annex, must be running erpcd with the bfs program
enabled. A UDP port (121) for erpcd must be defined in the services
database and the eservices file must be configured properly.
For expert C coders only: the host erpcd daemon can implement
macros, extended commands, command logging, and arbitrary
security restrictions through a set of interface routines to the Annex
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 A-325 and Modifying the Code on page A-335).

Table C-36. Supported Arguments for erpcd

Argument
Description
–Dlevel
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. For each
level, specify a D. For example –DD specifies 2 levels.
Note that there is no spece between the Ds.
–c maxnumber
Specifies the maximum number of child processes that
erpcd can create (for handling simultaneous requests).
–d udpport
Specifies a UDP port number; the default is 121.
(continued on next page)
Book C

Advertisement

Table of Contents
loading

Table of Contents