Open System Services NFS Management and Operations Guide

Commands That Operate on NETGROUP Objects
You can alter NETGROUP objects as the security requirements of the users and the network change.
These SCF commands operate on NETGROUP objects:
Allows a group of hosts or other netgroups access to the OSS NFS subsystem under a
new netgroup name.
ADD NETGROUP
Modifies membership of a netgroup.ALTER NETGROUP
Removes the specified NETGROUP object from the OSS NFS subsystem. This command
does not remove the capability to access the OSS NFS subsystem by user, group, or
DELETE NETGROUP
netgroup members of the deleted netgroup. Such access can be removed only with DELETE
commands that specifically name the users, groups, or netgroups to be removed.
Reports the members of the specified NETGROUP object.INFO NETGROUP
Reports the names of the NETGROUP objects that meet specified criteria.NAMES NETGROUP
SUBSYS Object
The SUBSYS object represents the OSS NFS subsystem as a whole. There is only one object of this
type in the OSS NFS subsystem.
Configuration and Prerequisites
Running the OSS NFS manager process creates the SUBSYS object, after which the SUBSYS object
is left in the STOPPED state. It must subsequently be started using the START SUBSYS command or
by starting any subordinate object such as a SERVER object.
Commands That Operate on the SUBSYS Object
The SUBSYS object gives you control of mount requests throughout the subsystem. Using
ALLOWOPENS and STOPOPENS commands, you enable and disable mount-request processing.
A TACL RUN command starts the OSS NFS manager process, which brings up the OSS NFS
subsystem in a STOPPED state. A START SUBSYS command is then normally used to start a previously
initiated subsystem and concurrently bring up all previously running objects. For initiating a new
subsystem, see the START SUBSYS command description in the Open System Services NFS SCF
Reference Manual.
These SCF commands operate on the SUSBSYS object:
Immediately terminates the operation of the OSS NFS subsystem, halting any requests
and services in process. OSS NFS data integrity is preserved, but client applications
ABORT SUBSYS
might be disrupted. All OSS NFS objects are left in the STOPPED state. To initiate the
operation of an aborted OSS NFS subsystem, you must restart the OSS NFS manager
process using a TACL RUN command. After the OSS NFS manager process is restarted,
the OSS NFS subsystem can be restored to the same state it was in prior to the ABORT
SUBSYS command by using the START SUBSYS command.
Reverses the effect of the STOPOPENS SUBSYS command and allows the OSS NFS
subsystem to accept new mount requests.
ALLOWOPENS SUBSYS
Allows changes to the REUSE-SERVERID flag. This flag determines whether any server
in the subsystem can be renamed. Such renaming can materially affect clients, so the
normal convention is to prevent such changes by leaving REUSE-SERVERID on.
ALTER SUBSYS
Returns a list of existing remote mounts. Use this command to verify that all remote
mounts have been unmounted before using the STOP SUBSYS command.
LISTOPENS SUBSYS
Reports the names of the subordinate processes, LANs, and servers in the subsystem.
You can limit the report to only those objects in selected states.
NAMES SUBSYS
Restarts a stopped OSS NFS subsystem, including all restartable LAN interface
processes and server processes that were in the STARTED state when the STOP SUBSYS
START SUBSYS
SCF Commands for OSS NFS Objects 33