File system |
||
| Create New Directories in Unicode
Default NT user for unknown UNIX user Default UNIX user for unknown NT user Minutes a cred cache entry is valid
|
This screen enables you to control miscellaneous aspects of
the filer's file system. To reload the current settings from the filer, click the Reload Settings button. To view the changes that you made, click the View Changes button. After you make a change, click the Save Changes button to save the changes to the filer. Create New Directories in UnicodeAbout UnicodeUnicode is a 16-bit character encoding system that includes all major languages. It is used by WIN 32 applications and file names in the following systems:
Unicode-format directories can contain file names in Unicode; other directory formats on the filer can't. Unicode-format directories can also contain file names in ASCII. Unicode-format directories are slightly larger than other directories. It can take several minutes to convert large directories to Unicode format; creating Unicode-format directories means fewer directories to convert. Unicode directory conversion choicesYes causes all new directories to be created in Unicode format. You choose this to facilitate file-sharing and eliminate conversion time. No causes the following behavior:
You choose No to save space or if do not use your filer for CIFS. Map NT Administrator to rootYes maps a Windows NT administrator to UNIX root. You should choose Yes to allow some filer administration from Windows NT clients. No does not do the mapping or stops the mapping, and prevents Windows NT administrator accounts from accessing administrative functions on the filer. Default NT User for unknown UNIX userType into this field the Windows NT user account to use when a UNIX user accesses a file with Windows NT security (has an ACL), and that UNIX user would not otherwise be mapped. If you leave this field blank, such accesses are denied. Default UNIX User for unknown NT userType into this field the UNIX user account to use when a Windows NT user attempts to log in and that Windows NT user would not otherwise be mapped. If you leave this field blank, such accesses are denied. Minutes a cred cache entry is validAbout the cred cacheIf a user is using UNIX and tries to open a file with an ACL in a mixed or NTFS (Windows NT security style) qtree, the filer uses NTFS security semantics to determine whether the user has access to the file. The filer does this by converting the UNIX UID (User ID) into a Windows NT credential, which is also known as a WAFL (Write Anywhere File Layout) credential. Windows NT uses the credential to verify that a user has access rights to the file. A UNIX user can have both a UNIX name and a Windows name. Windows NT verifies each request for access to files. Each access usually takes between 10 and 500 milliseconds, and can take longer because contacting a domain controller to create a WAFL credential is time-consuming. To reduce the time spent in contacting a domain controller, the filer can cache the WAFL credential in a credential cache. This cache is called the WAFL credential cache, or simply the cred cache. Cred cache entry validity timeYou control how long a WAFL credential remains in the cache and, therefore, remains valid, by typing in this field the number of minutes you want credentials to be valid. The default is 20 minutes. After a credential has been in the cred cache the amount of time you specify, it is removed. Windows NT verifies a credential when it is used the first time. The longer the credential in in the cache, the fewer the resources needed for credential verification, and the better the performance that the user experiences. If you need to see security updates as they occur, you might want to use less time than the default. However, with a smaller value, users might experience slower performance. Maximum Directory File SizeType into this field the maximum size, in kilobytes, you want for a directory file. The default, which is 10,240, means that the directory can hold about 300,000 files. NOTE: You can configure this field only if CIFS is not running. Cluster considerationsIn a cluster, the Maximum Directory File Size field must have the same value on both filers for takeover to occur properly. |