Open System Services NFS SCF Reference Manual

SCF Commands for OSS NFS
Open System Services NFS SCF Reference Manual—522582-001
2-90
Example
running. To stop a SERVER object without clearing the RESTART attribute, use the
STOP SUBSYS command.
•
For SERVER objects, active NFS requests are requests in progress.
°
A normal stop succeeds only if there are no active requests.
°
An orderly stop causes the server to enter the STOPPING summary state, reject
new requests, and wait for all active requests to complete before stopping the
server process.
°
A forced stop causes the server to enter the STOPPING summary state, reject
new requests, and aborts all active requests before stopping the server process.
•
While a SERVER object is stopped, no corresponding server process exists, and
therefore no Remote Procedure Call (RPC) calls, which deal with the directories
and files serviced by that process, can be accepted.
•
Use the START SERVER command to reinitiate the operation of the stopped server.
•
Use the STATUS SERVER command to determine the current summary state of the
SERVER objects.
•
Use the INFO SERVER command to determine the current attribute values of
SERVER objects.
•
Use the DELETE SERVER command to remove a SERVER object from the OSS
NFS subsystem.
Example
The following command terminates the operation of a server named $ZNFS.SRV1:
->STOP SERVER $ZNFS.SRV1
STOP SUBSYS Command
The STOP SUBSYS command terminates the operation of the OSS NFS subsystem in a
controlled manner. The STOP SUBSYS command does not abruptly terminate in-
progress activities.
Stopping the SUBSYS object causes all SERVER objects (all server processes), all LAN
objects (LAN interface processes), and the PROCESS object to be placed in the
STOPPED summary state.
The STOP SUBSYS command has the following syntax:
STOP SUBSYS process-name [ , ORDERLY | , FORCED ]
[ , SUB [ ALL | NONE | ONLY | subtype ] ]
[ , SEL [ NOT ] state ]