Introducing Network File System Version 4 on HP-UX 11i v3

14
Figure 13. GETATTR opcode reply
Figure 13 contains the results of a GETATTR opcode request. The GETATTR opcode was sent as part
of the close() system call. The results to the GETATTR opcode begins on line 11. The value of the
file’s owner and group appear on lines19 through 26. In this case, the UID and GID are
“[e-mail]“ and “[e-mail],” respectively.
Because the underlying file systems on HP-UX systems continue to use integer-based UIDs and GIDs,
NFSv4 must perform translations between the string identifiers and their corresponding 32-bit integer
UID and GID values. For example, if a file is being created, the NFS server must map the string
[e-mail] to the 32-bit UID that matches user1 on the system. This translation is done by the
nfsmapid daemon.
Mounting an NFSv4 file system on your HP-UX 11i v3 client
NFSv4 on HP-UX 11i v3 clients is disabled by default. Similar to enabling NFSv4 on HP-UX 11i v3
servers, enabling NFSv4 on HP-UX 11i v3 clients requires setting the configuration variable
NFS_CLIENT_VERSMAX to 4 in the configuration file, /etc/default/nfs, and restarting the NFS client
services using the startup and shutdown script, /sbin/init.d/nfs.client, with the stop and start
parameters.
To enable only NFSv4 on HP-UX 11i v3 clients, set both the configuration variables
NFS_CLIENT_VERSMIN and NFS_CLIENT_VERSMAX to 4.
Similar to NFS_SERVER_VERSMIN and NFS_SERVER_VERSMAX, NFS_CLIENT_VERSMIN and
NFS_CLIENT_VERSMAX control the range of protocol versions that your HP-UX 11i v3 client uses. For