Open System Services NFS Overview

Document Organization
“Introduction to NFS for Open System Services” (page 9)
Provides a general description of OSS NFS and OSS file storage on a NonStop system. It also
shows by example how files are mounted on UNIX systems and on NonStop systems through
OSS NFS.
“Security Mechanisms” (page 15)
Describes the security mechanisms used by OSS NFS.
“Troubleshooting for Client Users” (page 19)
Provides information about troubleshooting NFS client problems.
“NFS Protocol Description” (page 21)
provides information about the NFS protocols implemented by NFS for Open System Services.
Notation Conventions
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS
Uppercase letters indicate keywords and reserved words. Type these items exactly as shown.
Items not enclosed in brackets are required. For example:
MAXATTACH
Italic Letters
Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in
brackets are required. For example:
file-name
Computer Type
Computer type letters indicate:
• C and Open System Services (OSS) keywords, commands, and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For example:
Use the cextdecs.h header file.
• Text displayed by the computer. For example:
Last Logon: 14 May 2006, 08:02:23
• A listing of computer code. For example
if (listen(sock, 1) < 0)
{
perror("Listen Error");
exit(-1);
}
Bold Text
Bold text in an example indicates user input typed at the terminal. For example:
ENTER RUN CODE
?123
CODE RECEIVED: 123.00
The user must press the Return key after typing the input.
[ ] Brackets
Brackets enclose optional syntax items. For example:
Document Organization 5