Open System Services NFS SCF Reference Manual

SCF Commands for OSS NFS
Open System Services NFS SCF Reference Manual—522582-001
2-91
Considerations
SUBSYS process-name
specifies the name of the SUBSYS object whose operation is to be terminated. The
SUBSYS object uses the name of the manager process with which it is associated.
ORDERLY
specifies that the STOP operation rejects new requests, and waits for all active links
to be dropped before terminating the object. If you omit ORDERLY, the STOP
operation succeeds only if no active links exist when you issue the command.
FORCED
specifies that the STOP operation rejects all new requests, and aborts all active links
before terminating the object. If you omit the ORDERLY or FORCED option, the
STOP operation succeeds only if no active links exist when you issue the command.
SUB [ ALL | NONE | ONLY | subtype ]
specifies the subordinate object select option. You can use the SUB option to specify
that you want to stop only specified subordinate objects. The command STOP
SUBSYS, SUB ALL is equivalent to STOP SUBSYS, because no further commands
can be processed after the subordinate PROCESS object is stopped. With the STOP
SUBSYS command, only the SUB NONE, SUB ONLY, SUB LAN, and SUB
SERVER options are useful.
SEL [ NOT ] state
specifies the summary state select option. You can use the SEL option to specify that
you want to stop only objects in the STARTED summary state.
Considerations
Consider the following points when using the STOP SUBSYS command:
•
STOP SUBSYS is a sensitive command requiring super-group access.
•
To stop the SUBSYS object immediately, despite active links, use the ABORT
SUBSYS command.
•
For the SUBSYS object, active links are remote mounts.
°
A normal stop succeeds only if there are no remote mounts against any part of
the OSS NFS subsystem.
°
An orderly stop causes the subsystem to enter the STOPPING summary state,
reject new mounts, and wait for all current mounts to be unmounted. After all
remote mounts have been unmounted and all subsidiary LAN and SERVER
objects have stopped, the manager process stops.
°
A forced stop causes the subsystem to enter the STOPPING summary state,
reject new mounts, and abort all current mounts. After all remote mounts have
been unmounted and all subsidiary LAN and SERVER objects have stopped, the
manager process stops.