Open System Services NFS SCF Reference Manual

Introduction
Open System Services NFS SCF Reference Manual—522582-001
1-4
Object-Name Syntax
EXPORT Identifies a server mount point, and all the files managed by that server
that are to be exported.
Note that although you can define EXPORT objects for non-existent
directories or directories that are not server mount points these EXPORT
objects are ignored. Export permissions are only checked by the NFS
manager process for the mount point of the server responsible for the
directory being remotely mounted.
GROUP Identifies a group of NFS users.
LAN Identifies the local area network (LAN) interface process that acts as a
front end for NFS requests received from the NonStop™ TCP/IP
communications process.
NETGROUP Identifies a group of host machines and users within specified network
domains. Netgroups can be used in the access lists attached to EXPORT
objects.
SERVER Identifies a server process. An OSS NFS server provides access to a
specific OSS file set. Each server has an attribute that identifies a mount
point within the local hierarchy; that is, the hierarchy of the system on
which the OSS NFS subsystem is operating. A local mount occurs
whenever a server is started.
USER Identifies an NFS user by a user name and user number.
To control the OSS NFS subsystem, you use the SCF commands documented in
Section 2, SCF Commands for OSS NFS
. As shown in Section 2, the syntax of each
command contains the variable object-spec, which you use to specify the type and
name of the object on which you want the command to operate.
You do not need to specify an object type for any command that supports the NULL
object. In OSS NFS, these commands are NAMES and VERSION. The NULL object
is not within the object-type hierarchy.
Object-Name Syntax
The syntax and rules for specifying OSS NFS object names vary slightly from the
standard SCF object-name syntax. The original SCF object-name design was intended
to cover two types of object names: Enscribe file names and simple subsystem-defined
object names. To handle NFS path names (which can be up to 1024 characters long and
can contain any character except ASCII NUL), this design had to be expanded.