| Skip Navigation Links | |
| Exit Print View | |
|
ONC+ Developer's Guide |
1. Introduction to ONC+ Technologies
4. Programmer's Interface to RPC
5. Advanced RPC Programming Techniques
6. Porting From TS-RPC to TI-RPC
7. Multithreaded RPC Programming
8. Extensions to the Sun RPC Library
B. RPC Protocol and Language Specification
F. Writing a Port Monitor With the Service Access Facility (SAF)
Restricting Access to the System
Port Monitor Process IDs and Lock Files
Changing the Service Environment: Running doconfig()
Port Monitor Administrative Interface
SAC Administrative File _sactab
Port Monitor Administrative File _pmtab
SAC Administrative Command sacadm
Port Monitor Administrative Command pmadm
Monitor-Specific Administrative Command
Port Monitor/Service Interface
Configuration Files and Scripts
Interpreting Configuration Scripts With doconfig()
Per-Port Monitor Configuration Files
Per-Service Configuration Files
Printing, Installing, and Replacing Configuration Scripts
Per-System Configuration Scripts
Per-Port Monitor Configuration Scripts
Per-Service Configuration Scripts
This section briefly covers the files used by the SAF.
A port monitor's current directory contains an administrative file named _pmtab. _pmtab is maintained by the pmadm command in conjunction with a port monitor-specific administrative command.
The port monitor administrative command for a listen port monitor is nlsadmin(); the port monitor administrative command for ttymon is ttyadm(). Any port monitor written by a user must be provided with an administrative command specific to that port monitor to perform similar functions.
A port monitor's current directory also contains the per-service configuration scripts, if they exist. The names of the per-service configuration scripts correspond to the service tags in the _pmtab file.
A port monitor can create private files in the directory /var/saf/tag, where tag is the name of the port monitor. Examples of private files are log files or temporary files.
|