ptx/NFS V4.6.4 Release Notes

ptx®/NFS® V4.6.4 is a subset of Sun Microsystems® NFSSRC V4.2, ported and enhanced to run on NUMA-Q® and Symmetry® systems. It supports filesystems larger than 2 GB and files up to 2 GB.


Product Compatibility

This version of ptx/NFS requires the following products:

For product compatibility with other DYNIX/ptx products, consult the DYNIX/ptx and Layered Products Software Installation Release Notes.


Software Installation

For information on installing ptx/NFS, refer to the DYNIX/ptx and Layered Products Software Installation Release Notes.

For ptx/NFS, you will need 3.2 MB in root and 8.8 MB in /usr.


Related Documentation

For more information about ptx/NFS and NIS+ products, refer to the following manuals:


Problem Reports

This section lists fixed and open software defects that have been reported against this release of ptx/NFS.


Fixed Software Defects in ptx/NFS V4.6.4

The following software defects are fixed in ptx/NFS V4.6.4:


Open Software Defects in ptx/NFS V4.6.4

This section describes known software defects in this release of ptx/NFS. The number that appears in parentheses in the title of each problem report is the problem-tracking-system number assigned to the report.


ptx/ADMIN Menus Create auto.master Files Instead of auto_master Files (248901)

The ptx/ADMIN menus used to manage the automounter maps create file names with periods instead of underscores, creating /etc/auto.master instead of /etc/auto_master.

Workaround. None.


ptx/ADMIN Does Not Allow More than 10 Hosts in the Read/Write Group (248473)

ptx/ADMIN returns an error when a user tries to add more than 10 hosts in the "Enter list of hosts to export this filesystem read/write to" section of the "Exported filesystems" menu. The error is:

Too many members in the read/write group
Must be less than 10. Operation aborted.

Workaround. If you wish to place more than 10 hosts in the read/write group, edit the /etc/exports file manually and then run exportfs.


The Automounter Does Not Understand NIS Maps (246901)

The automounter is not able to read maps from NIS servers.

Workaround. None.


rpcinfo Cannot Communicate with Previous Version of Portmapper (245483)

rpcinfo is unable to communicate with previous versions of the portmapper.

Workaround. None.


mount_nfs Returns 0 Exit Status When it Fails (242140)

The mount_nfs command returns a 0 exit status when it fails because the mount point is already in use. This can cause problems when mount_nfs is used by shell scripts that try to verify whether the command was successful.

Workaround. None.


ptx/NFS Limits Itself to One-Half the Total Buffer Cache (240556)

ptx/NFS limits itself to one-half the total buffer cache. This does not work correctly on multiquad systems, where one quad can run out of buffers.

Workaround. None.


mount_nfs Does Not Validate Options (239483)

The mount_nfs command does not validate the options that are passed to it and passes bad options to /etc/mnttab.

Workaround. None.


Environment Macro Expansion Not Working Correctly in Automounter (239476)

Environment macro expansion in the automounter does not work correctly.

Workaround. None.


The Automounter Cannot Start Up with "-p <port> number" (239389)

One of the options in the automounter is to start up the automounter server with a known port number and replace a crashed automounter with the same port number. However, the automounter refuses to start up with the -p option.

Workaround. None.


The Automounter Has Problems with auto.master File Options (239314)

When you create an automount setup through ptx/ADMIN and use direct or indirect maps, the option for the type of mount is positionally dependent. If the mount type is last on the line, it will generate errors in the ktlog.

Workaround. None.


automount Man Page Does Not Document Options Correctly (239277)

The -f, -p, and -l options to the automount command are not documented in the man page.

Workaround. None.


Comments in the auto.master File Are Not Ignored by the automounter (239176)

Comments in the auto.master file are not ignored by the automounter, which results in errors in the ktlog.

Workaround. None.