This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. Network File System

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:

Temporary Waivers

1.1 XNFS Service Model

1.1.1 XNFS Objects

Question 1: Which of the following ExportedFileSystem attributes have the recommended default values?

Response

Attribute	Recommended Default Value	Recommended Default Implemented
Mode	ReadWrite	Yes No Variable
AnonMapping	-2	Yes No Variable
Root	All UID 0 accesses mapped	Yes No Variable
Access	Accessible to all clients	Yes No Variable

Rationale

An XNFS client must implement a minimum set of ExportedFileSystem attributes which includes those listed above. These have recommended default values but clients can define recommended values that are different. AnonMapping may be -1, meaning disable anonymous access to the file system, or the server may provide a mechanism to change this mapping to any UID.

Root and Access can be lists of hostnames and hosts/groups, respectively. These will depend on your system's environment and connectivities.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 2.4.1, ExportedFileSystem.

Question 2: Which of the following MountedFileSystem attributes have the recommended default values?

Response

For each entry, select Yes, No, or Variable. Note that Mode, GrpID, SetUID, NFSRetrySemantics, Intr and AttribCaching should not be set to "Variable."

Attribute	Recommended Default Value	Recommended Default Implemented
Mode	ReadWrite	Yes No Variable
GrpID	False	Yes No Variable
SetUID	False	Yes No Variable
NFSTimeOut	7 tenths of a second	Yes No Variable
NFSRetransmissions	3 times	Yes No Variable
NFSRetrySemantics	Hard	Yes No Variable
Intr	False	Yes No Variable
NFSServerPort	2049	Yes No Variable
AttribCaching	False	Yes No Variable
ACRegMin	Hold >= 3 Seconds	Yes No Variable
ACRegMax	Hold <= 60 Seconds	Yes No Variable
ACDirMin	Hold >= 30 Seconds	Yes No Variable
ACDirMax	Hold <= 60 Seconds	Yes No Variable

If any of the above were marked "Variable", supply a description of the manner in which variations occur in the area below.

Rationale

An XNFS client must implement a minimum set of MountedFileSystem attributes which includes those listed above. These have recommended default values but clients can define recommended values that are different.

When GrpID is False then the group ID of any file or directory created on the system is set to the group of the current process or the parent directory, as specified by XSI.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 2.4.2, MountedFileSystem.

1.1.2 XNFS Server Administration Operations

Question 3: Which of the following optional administration operations are provided?

Response

Operations	Meaning	Provided
UnExpFileSysOp	Un-export file system	Yes   No
ExpStdFileSysOp	Export StandardExports file system set	Yes   No
UnExpStdFileSysOp	Un-export StandardExports file systems	Yes   No

Rationale

Only the ExpFileSysOp operation is mandatory. Those listed above may be provided additionally.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 2.5, XNFS Server Operations.

1.1.3 XNFS Client Administration Operations

Question 4: Which of the following optional administration operations are provided?

Response

Operations	Meaning	Provided
MntStdFileSysOp	Mount StandardMounts file system set	Yes   No
UnMntallFileSys	Unmount some or all mounted file systems	Yes   No

Rationale

These operations are listed as optional.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 2.6, XNFS Client Operations.

1.2 Optional Server Functionality

1.2.1 Permission Issues

Question 5: Does the server use AUTH_UNIX style authentication?

Response

Yes   No

Rationale

This is described as the expected behaviour and informs the list of likely functional differences, for various utilities and functions, given in Appendices A, B and C. It may also affect the networking environment required for correct access control over XNFS.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 4.4, Authentication Protocols and Section 7.4, NFS Implementation Issues.

Question 6: Does the server allow the owner of a file to access it regardless of its permissions?

Response

Yes   No

Rationale

This is required to preserve the stateful nature of open which may be depended on by some applications. If an application does not remove required access to a file while it is still open, and does not still expect to access it, then the answer to this question can be No. Applications that do require this behaviour, and hence the answer Yes, will be less portable.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 7.4, NFS Implementation Issues.

Question 7: Does the server provide a mechanism to change the mapping of user id 0?

Response

Yes   No

Rationale

An XNFS server, by default, maps the user id 0 to -2 (0xfffffffe) before doing its access checking. A server implementation may provide a mechanism to change this mapping.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 7.4, NFS Implementation Issues.

1.2.2 Server Procedures

Question 8: Does your server support symbolic links?

Response

Yes   No

Rationale

A conforming system that does not support symbolic links should return a PROC_UNAVAIL error if a client issues an NFSPROC_READLINK or NFSPROC_SYMLINK.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 7.5.6, NFSPROC_READLINK Specification and Section 7.5.14, NFSPROC_SYMLINK Specification.

1.2.3 File Locking over XNFS

Question 9: Which of the following levels of file and/or record locking does your system provide, in an XFNS environment?

Response

Locking Service	Provision
No Locks	Yes   No
Monitored Locks	Files Records Both None
Un-monitored Locks	Files Records Both None

Rationale

A conforming system must provide at least one of these levels of locking. Monitored locks are preferred over non-monitored locks but require NSM service on both client and server hosts.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Chapter 9, File Locking over XNFS.

Question 10: Are locks created by DOS processes honoured by processes running on an X/Open host and vice versa?

Response

Yes   No

Rationale

It is also recommended, but not required, that locks created by DOS processes are honoured by processes running on an X/Open host and vice versa.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Chapter 9, File Locking over XNFS.

1.2.4 Network Lock Manager

Question 11: What is the duration of the grace period after an XNFS server crash on your system?

Response

This question is only relevant if access to the nlm is required to implement locking. Normally locks are provided to applications by their using fcntl or equivalent XSI routines, and hence the question is not relevant. In this case enter "N/A" on the line below. Otherwise, enter the number of seconds allowed as a grace period or "Variable" if this is not a defined period. If the answer is "Variable", please also supply a description of the manner in which variations occur.

Rationale

The duration of the grace period is implementation-dependent; 45 seconds is common.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 10.1.2, Synchronisation of NLMs.

Question 12: What are the names of the enumeration constants in nlm_stats?

Response

For each entry in the table below enter the name of the equivalent enumeration constant in your implementation. If locking is not supported, enter "N/A".

X/Open Name	Value	Your Equivalent Name
LCK_GRANTED	0
LCK_DENIED	1
LCK_DENIED_NOLOCKS	2
LCK_BLOCKED	3
LCK_DENIED_GRACE_PERIOD	4

Rationale

Note that some versions of NFS source may use mixed or lower-case names for the enumeration constants in nlm_stats.

Reference

CAE Specification, Protocols for X/Open Interworking: XNFS, Section 10.2.2, Basic Data Types for Locking, nlm_stats.

2. Appendix

Copyright © 
All rights reserved.

3. Change History