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.
When sharing objects, NFS clients running Linux 2.6 may receive incorrect “permission denied” errors when they try to update files owned by other users: If you have setup the NFS server of Mac OS X Leopard and try to edit the contents of a file from an NFS client machine running Linux 2.6 with an application program which updates in place, and you have write permission although the file is owned by another user, the client may receive a false "permission denied" response from the server.
Workaround: This is a known defect of Mac OS X Leopard. In certain cases, application programs on the Linux side can be reconfigured not to update files in place but to write them in a “rename previous version, save the new version” sequence. This could be a workaround, but only works in a few cases. Apple is aware of this problem and might fix it in future versions of Mac OS X.
When downloading music tracks from the iTunes Store onto an NFS file system, Mac OS X Leopard may damage the downloaded files: If you are using an NFS client running Mac OS X Leopard and a version of iTunes which is configured to store its media library onto an NFS file system (which is the standard setup for a network user with an NFS home folder), successfully purchasing music from the iTunes Store might not be possible. After downloading the music tracks, iTunes performs post-processing on the files which can corrupt the data. The tracks can become unplayable or may show audible glitches like skipped passages, clicks, high-frequency noise, etc.
Workaround: Use Mac OS X Tiger, or ensure that iTunes downloads the music tracks onto the local hard drive. Apple is aware of this problem and might fix it in future versions of Mac OS X.
The Finder may fail to re-trigger automounts after such mounts have expired. It might display nonsense messages instead: If you have defined an automatic connection to an NFS server, this connection had been in use, but then the connection expired because no file of it has been accessed for more than one hour, the Finder might fail to automatically reconnect to the server when you click on the icon of the mount point. In this case you may receive incorrect error messages, e.g. that you have selected an invalid alias, that the clicked object cannot be found, or that an object named “” is no longer available.
Workaround: When using Mac OS 10.5.x, a second click on the object might succeed and the automount will be reconnected. With Mac OS X 10.6.x, restarting the Finder might help, but not always. The best solution is to launch NFS Manager, select the affected entry in the automount table and to press the button Trigger selected mount now. Apple does not disclose any information if and when this bug will be fixed.
In Mac OS X Snow Leopard, the Finder might display objects for file servers which have been disconnected already: Under particular circumstances, the Finder of Mac OS X 10.6.x may display files and folders on remote servers even after the connection to the server has been closed. The objects are in fact inaccessible or no longer exist.
Workaround: When you are experiencing this problem, press ⌘+⌥+esc and restart the Finder. Apple does not disclose any information if and when this bug will be fixed.
When removing or redefining automount entries, the automounter of Mac OS X may not unmount or remount the affected entries immediately: If you make multiple changes to automount entries, saving modified configurations in rapid succession, your changes may not become effective immediately. Active automounts whose entries have been removed don't unmount but keep connected, changed parameters for active automounts won't be respected. When triggering automounts via NFS Manager, you may receive the message that an unexpected problem occurred and that the object expected at the mount point location could not be found.
Workaround: The problem is caused by architectural issues in the way the automounter components and directory services communicate with each other, and how they cache information. If you are under the impression that the automounter ignores all your changes after a certain point of interaction, reboot the operating system to enforce that your changes take effect.