B.2 Samba and NSS Volumes

Be aware of the following when using Samba to access NSS volumes.

B.2.1 Access Requires Additional Setup

Samba-enabled users cannot access an NSS volume using Samba until they are granted NSS trustee rights to the volume. (Rights are automatically granted for home directories on NSS volumes that are created in iManager.)

You can grant NSS trustee rights on a per-object basis using either the ncpcon > rights command at the OES Linux server shell prompt or by using an NCP client (provided the NCP server is running at the time).

If you are granting the same rights to multiple Samba users, it is more efficient to assign those users to a LUM-enabled group and then grant trustee rights to the group. Keep in mind that each group member has the same rights in this case.

For more information on granting NSS trustee rights, see Using the Novell Client to Manage Trustees and Trustee Rights and Trustee Rights Utility for Linux in the File Systems Management Guide for OES.

B.2.2 Mounting NSS Volumes for Use with Samba

Because Windows is case insensitive, we strongly recommend that you mount NSS volumes as case insensitive when they are accessed through Samba.

When mounting an NSS volume for use with Samba:

  1. In iManager > the Storage plug-in > Volumes > Properties, set the Lookup Namespace option to Long and remount the volume.

  2. On the OES Linux server, open the /etc/samba/smb.conf file in a text editor and check for a case sensitive parameter in [global] section of the file. If the parameter exists (normally it does not) and if it is set to yes, change the setting to no.

B.2.3 Samba on NSS Can Be a Good Combination for Performance

If you will have more than 2,000 files and folders accessed through Samba, you should consider using NSS as the underlying file system. Above that number, Samba on NSS outperforms Samba on traditional Linux volumes, such as EXT3 or Reiser. As you add more files and directories above the 2,000 mark, the performance advantage increases.