| 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 File
Per-Service Configuration Files
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
A port monitor must terminate itself gracefully on receipt of the signal SIGTERM. The termination sequence is as follows:
The port monitor enters the stopping state. No further service requests are accepted.
Any attempt to re-enable the port monitor is ignored.
The port monitor yields control of all ports for which it is responsible. A new instantiation of the port monitor must be able to start correctly while a previous instantiation is stopping.
The advisory lock on the process ID file is released. After this lock is released, the contents of the process ID file are undefined and a new invocation of the port monitor can be started.
|