| |
Home About Us A-Z Index Search • |
Organization | SCO |
---|---|
Author | Nadeem Wahid |
Product Identification | Version/Release Number | Product Supplier | |
---|---|---|---|
1. | UnixWare | 7.1.0 | SCO |
Testing Environment | Binary-compatible Family | Portability Environment | Indicator of Compliance | Compliance Details | |
---|---|---|---|---|---|
1. |
|
| Select from this list ,Internationalised System Calls and Libraries Extended | Test Report from Test Suite | Test Suite:
VSX4.4.3+XNFS Test Report: UW710_XNFS |
Question 1: Which of the following ExportedFileSystem attributes have the recommended default values?
Response
Attribute | Recommended Default Value | Recommended Default Implemented |
---|---|---|
Mode | ReadWrite | Yes |
AnonMapping | -2 | No |
Root | All UID 0 accesses mapped | Yes |
Access | Accessible to all clients | Yes |
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
Attribute | Recommended Default Value | Recommended Default Implemented |
---|---|---|
Mode | ReadWrite | Yes |
GrpID | False | Yes |
SetUID | False | No |
NFSTimeOut | 7 tenths of a second | No |
NFSRetransmissions | 3 times | No |
NFSRetrySemantics | Hard | Yes |
Intr | False | Yes |
NFSServerPort | 2049 | Yes |
AttribCaching | False | Yes |
ACRegMin | Hold >= 3 Seconds | Yes |
ACRegMax | Hold <= 60 Seconds | Yes |
ACDirMin | Hold >= 30 Seconds | Yes |
ACDirMax | Hold <= 60 Seconds | Yes |
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.
Question 3: Which of the following optional administration operations are provided?
Response
Operations | Meaning | Provided |
---|---|---|
UnExpFileSysOp | Un-export file system | Yes |
ExpStdFileSysOp | Export StandardExports file system set | Yes |
UnExpStdFileSysOp | Un-export StandardExports file systems | 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.
Question 4: Which of the following optional administration operations are provided?
Response
Operations | Meaning | Provided |
---|---|---|
MntStdFileSysOp | Mount StandardMounts file system set | Yes |
UnMntallFileSys | Unmount some or all mounted file systems | No |
Rationale
These operations are listed as optional.
Reference
CAE Specification, Protocols for X/Open Interworking: XNFS, Section 2.6, XNFS Client Operations.
Question 5: Does the server use AUTH_UNIX style authentication?
Response
Yes
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
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
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.
Question 8: Does your server support symbolic links?
Response
Yes
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.
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 | No |
Monitored Locks | Both |
Un-monitored Locks | Both |
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
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.
Question 11: What is the duration of the grace period after an XNFS server crash on your system?
Response
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
X/Open Name | Value | Your Equivalent Name |
---|---|---|
LCK_GRANTED | 0 | nlm_granted |
LCK_DENIED | 1 | nlm_denied |
LCK_DENIED_NOLOCKS | 2 | nlm_denied_nolocks |
LCK_BLOCKED | 3 | nlm_blocked |
LCK_DENIED_GRACE_PERIOD | 4 | nlm_denied_grace_period |
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.
Copyright © The Santa Cruz Operation, 1998
All rights reserved.
Date | Name | Comment |
---|---|---|
09-Dec-1998 | Joanna Farley (SCO) | First Version |
The Open Group and Boundaryless Information Flow are trademarks and UNIX is a registered trademark of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.