Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Starting an OSS SEEP
The OSS name server starts and manages the OSS SEEP. Each time the OSS name server starts
the OSS SEEP, it first attempts to kill any process with the same process name. An EMS message
notes this action. If the OSS name server determines that the OSS SEEP was not started, it does
not send messages to the OSS SEEP until it successfully kills the process and restarts it. Be careful
to avoid name collisions.
The OSS name server starts the OSS SEEP in the following conditions:
• When the OSS name server's SEEPENABLED attribute is set to ON, or changed from OFF to
ON, and an OSS SEEP-protected fileset is mounted under it
• During fileset mount, if all of the following conditions are true:
The fileset is OSS SEEP-protected.◦
◦ The associated OSS name server’s SEEPENABLED attribute value is ON.
◦ The OSS SEEP is not already running.
• When the SEEPPROTECTED attribute of a mounted fileset is set or changed from OFF to ON,
if all of the following conditions are true:
◦ The OSS name server’s SEEPENABLED attribute value is ON.
◦ The OSS SEEP is not already running.
• When receiving an OSS SEEP death message due to the OSS SEEP’s CPU failure or other
reasons
• During OSS name server takeover for either of the following conditions:
If the OSS SEEP goes down along with the primary OSS name server due to a CPU failure◦
◦ If the OSS SEEP needs to be started based on the current OSS SEEP state
During an OSS SEEP start, after the OSS name server creates the process and sends the startup
parameter message to the OSS SEEP. A handshake message is sent to determine the OSS SEEP’s
readiness to accept authorization requests.
The OSS SEEP runs with a userid of SUPER.SUPER.
The backup OSS name server does a backup open of the OSS SEEP when the primary OSS name
server completes the OSS SEEP start.
While attempting to start the OSS SEEP with the configured process name, if there is already a
process running with the same name, the OSS name server stops the process and starts the OSS
SEEP with that name. An EMS event is generated for notification that the running process was
stopped.
Stopping an OSS SEEP
When the OSS SEEP is required to be stopped, the OSS name server does a close of the OSS
SEEP and waits for the process death message. HP recommends that the OSS SEEP performs the
necessary cleanup and stops itself upon receiving the final close message. The following conditions
trigger an OSS SEEP stop:
• When the OSS name server's SEEPENABLED attribute is changed from ON to OFF
• During fileset unmount, if it is the only OSS SEEP-protected fileset mounted in the controlling
OSS name server
• When the SEEPPROTECTED attribute of a mounted fileset is changed from ON to OFF, if the
OSS SEEP is running and if there are no other OSS SEEP-protected filesets mounted under the
OSS name server
Protecting Your System 233