Technical Notes |
|
The Reflection NFS Client gives you two options for handling the case of file names on NFS servers: Optimize for case handling, and Optimize for performance. This technical note explains the two settings and how to change them.
UNIX and Windows handle file name case sensitivity differently, and some Windows applications (some 32-bit and all 16-bit) do not retain the case of file names.
By default, when you use Reflection NFS to access a file, Reflection does extensive internal file name matching to keep track of the case of file names on the NFS server. This functionality does come with some additional overhead, so Reflection also provides options that allow you to optimize this setting for your NFS environment.
The Reflection NFS Client gives you two options for handling the case of file names on NFS servers: Optimize for case handling, and Optimize for performance.
Read the descriptions below to determine the best configuration choice for case optimization in your environment, and then proceed to Configuring File Name Case Handling in Reflection NFS to verify or change your settings.
If you optimize for case handling rather than for performance, Reflection maintains the case of file names. However, to accommodate differences in case handling by Windows and UNIX, Reflection NFS performs file operations such as open, delete, and rename using case-insensitive searching.
An example of the differences in case sensitivity between the two operating systems can be demonstrated by the following scenario. Create a file on your local C: drive called abc.txt, then try to create a second file, in the same directory, called ABC.txt, Windows will tell you that there is already a file by that name. Do the same thing in UNIX (using a host emulator such as Reflection for UNIX and OpenVMS), and you will be able to create the two files. UNIX recognizes abc.txt and ABC.txt as two different files.
To avoid this conflict, make sure that all file names are unique by more than just case. (See the online help for further details regarding this topic and the related Check for Duplicate Names setting.)
If you choose to optimize for mixed case file names, Reflection NFS consumes more memory for storing file name information. This memory usage is temporary, but a UNIX host with many directories and large numbers of files (over 1,000) can cause Reflection NFS to consume several megabytes of RAM at times of heavy use. This can result in slower performance when saving files. This method does, however, provide more secure file protection than optimizing for performance.
If you choose to optimize for performance, Reflection NFS will consume less memory and therefore may perform faster in certain environments. However, this option has several consequences:
Generally, the default option (Optimize for case handling) is recommended. This option allows you to have mixed case file names on the NFS server and prevents you from overwriting files with names that differ only by case. You may want to choose Optimize for performance, however, if all of the following conditions are true:
The setting for file name case handling can be set globally (for all NFS connections) or individually (for each mapped NFS drive). The procedures for each method are presented in the next two sections.
Follow the steps below to verify or reconfigure file name case handling for all NFS connections in Reflection NFS Client.
In Windows XP, click Start > right-click My Network Places > Properties > right-click Local Area Connection > Properties > Reflection NFS Client > Properties.
In Windows 2000, right-click My Network Places > Properties > right-click Local Area Connection > Properties > Reflection NFS Client > Properties.
Follow the steps below to verify or configure file name case handling for individual mapped NFS drives.