The LAPSAFE
feature does not export an API directly. It modifies the function and semantics of local access point creation and invocation. In particular, it enables the K_LAP_SAFE
option (see svLapCreate(2K)), which causes validity checking to be turned on for an individual LAP
. If a LAP
is invalid or has been deleted, lapInvoke() will fail cleanly with an error return. Furthermore, the svLapDelete() call will block until all pending invocations have returned. This option
allows a LAP
to be safely withdrawn even when client actors continue to exist. It is useful for clean shutdown and reconfiguration of servers.
The LAPSAFE
feature is a prerequisite for HOT_RESTART
.
For more details, see LAPSAFE(5FEA).