NFS Manager
Known Issues
There are currently no known issues for this product.
Release Notes
Some applications cannot open files from an NFS server if those files have not been created using NFS: If you write a file with a Macintosh resource fork or extended Finder attributes to an NFS server without using NFS (e.g. using AppleShare, Windows sharing or by creating this file directly on the server writing it to the local hard disk), you may later have problems opening this file using NFS. Each file sharing protocol uses different techniques to handle forks and attributes. Those techniques are not compatible with each other, so you cannot write a file with resource fork or attributes using one protocol but read it with another protocol.
Workaround: You should avoid using different file server protocols at the same time when reading and writing Macintosh files with forks or Finder attributes.
When sharing objects which have permissions defined by ACLs, NFS clients may receive incorrect “permission denied” errors when trying to access the objects: If you have created an NFS share which includes objects that are using POSIX.1e permissions (Access Control Lists, ACLs), immature versions of Mac OS X Leopard may not be capable of handling the permissions correctly when clients are using NFS to access those objects. The clients receive false “permission denied” responses from the server, no matter what POSIX permissions and what ACL permissions are set.
Workaround: This is a known defect of early Mac OS X Leopard versions up to and including 10.5.2. Upgrade to Mac OS X 10.5.3 or higher to fix this problem.