JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
ONC+ Developer's Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


1.  Introduction to ONC+ Technologies

2.  Introduction to TI-RPC

3.  rpcgen Programming Guide

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

9.  NIS+ Programming Guide

A.  XDR Technical Note

B.  RPC Protocol and Language Specification

C.  XDR Protocol Specification

D.  RPC Code Examples

E.  portmap Utility

F.  Writing a Port Monitor With the Service Access Facility (SAF)

What Is the SAF?

What Is the SAC?

Basic Port Monitor Functions

Port Management

Activity Monitoring

Other Port Monitor Functions

Restricting Access to the System

Creating utmpx Entries

Port Monitor Process IDs and Lock Files

Changing the Service Environment: Running doconfig()

Terminating a Port Monitor

SAF Files

Port Monitor Administrative File

Per-Service Configuration Files

Private Port Monitor Files

SAC/Port Monitor Interface

Message Formats

SAC Messages

Port Monitor Messages

Message Classes

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

New Service Invocations

Standing Service Invocations

Port Monitor Requirements

Initial Environment

Important Files

Port Monitor Responsibilities

Configuration Files and Scripts

Interpreting Configuration Scripts With doconfig()

Per-System Configuration File

Per-Port Monitor Configuration Files

Per-Service Configuration Files

Configuration Language

assign Keyword

push Keyword

pop Keyword

runwait Keyword

run Keyword

Printing, Installing, and Replacing Configuration Scripts

Per-System Configuration Scripts

Per-Port Monitor Configuration Scripts

Per-Service Configuration Scripts

Sample Port Monitor Code

Logic Diagram and Directory Structure



Terminating a Port Monitor

A port monitor must terminate itself gracefully on receipt of the signal SIGTERM. The termination sequence is as follows:

  1. The port monitor enters the stopping state. No further service requests are accepted.

  2. Any attempt to re-enable the port monitor is ignored.

  3. 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.

  4. 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.