This section has NFS Server FAQs for Native File Access for UNIX.
If NetStorage is installed, then in NetStorage, beside where you view/modify NetWare attributes, there is a new tab to view/modify NFS Information.
This is because the UNIX client displays the cached results.
It does not issue an NFS call because the change in the NetWare owner metadata does not affect the modification timestamps. Therefore, the client assumes its cache to be valid and displays cached results.
When the client refreshes the cache it will display the updated information.
Alternately, execute a touch file/directory_name to force the updates.
When you unshare or remove a path from exports list, unmount all the client mounts for that share.
When you specify /pathname -ro -root, the path is exported as read-only with root access to all clients.
However, when you specify /pathname -ro -anon, the path is exported as read-only with anonymous access to all clients. If you do not specify the anon option, then on the client side root cannot do any operations on the mount point.Even executing a cd to the mount point is not allowed.
When you specify only -ro option for the pathname, it exports the path as read-only to all clients. Because by default, root-access and anonymous access are disabled, the root cannot perform any operations except mounting on the mount point.
The NFS Server on NetWare 6.5 does not support export of NetWare Traditional File system.
To avoid the issues, use AIX 5.0 or later NFS clients.
To resolve this and install the latest NFS iManager snap-ins after deleting the previous module.
To delete the module, go to iManager menu > Configure > iManager configuration > Modules.
Use iManager or language (i18n) enabled editors to export non-English paths.
NFS Server does not support export of directories with spaces in the name. Make sure that users do not export a directory containing spaces. If users try to export a directory with spaces in the name, the exports fails without any message displayed.
When the default umask of 022 is applied to the mount point, the non-root user must be the owner in order to have permission to work at the mount point.
To grant the non-root user permissions to perform all the operations:
After exporting a volume with root access and all rights, mount it on UNIX and execute a chmod nnn command along with a combination of chown and chgrp to the user’s UID/GID.
Umount the mount point.
Export the same volume again with rw permissions.
Mount it on UNIX.
NFS Server does not suppport the remote NIS feature.
To resolve this, modify etc\nfs.cfg and set NDS_ACCESS= 1 and restart nfsservices.
You can use the Ldapsearch tools to write all types of queries to get the information from eDirectory, including users and groups data. For more information on the Ldapsearch tools, refer the Novell eDirectory 8.6 documentation:Using LDAP Tools on Linux or Solaris.
This is because the NFS filehandle format has changed. To resolve this, unmount and remount the paths on the NFS clients.
This is because certain Windows based applications such as Wordpad do not actually modify files. When you save your modifications, they delete the original and save the modified version as a new file. Therefore, the new file gets the ownership of the modifying NetWare- windows user, and default permissions.
OES SP1 has the implementation of NSS hardlinks. For details on enabling hard link support for NFS, see Technical Information Document