The CIFS options control CIFS features on the filer.
Off
When On, enables the filer to process access logging, or auditing, information. The default is Off.
None
Specifies the active event log file. The file must be in an existing directory in a network share.
On
When On, directories in the path to a file are not required to have the 'X' (traverse) permission.
Note: This option does not apply in UNIX qtrees or volumes.
None
When you leave cifs.guest_account blank, a CIFS user can log in to the filer without an account in the password database, provided that a domain controller authenticates the user.
When you set cifs.guest_account to the name of an account in the NIS passwd map or /etc/passwd (typically guest), guest access to the filer is enabled, and the user has the UNIX user ID and the group ID of the guest account. For more information, see "Enabling guest and generic access."
None
Specifies the complete path name of the "homes directory." The directories under this path should have the names of users as their names. When a CIFS user connects to the filer and there is a directory name that exactly matches the user's name, the user sees a share of that name (truncated to 12 characters) that is the user's home directory. Only the user can access the home directory using this share. All other users are denied access.
18000
Specifies the number of seconds that elapse before the filer disconnects an idle session. The value can range from 600 through 4,000,000 (effectively infinite).
None
Specifies a list of alternative names for the filer. Use a comma-separated list of names.
On
When this option is On, the filer enables clients to use oplocks (opportunistic locks) on files. Oplocks provide a significant performance enhancement, but have the potential to cause lost cached data on some networks with impaired reliability or latency, particularly wide-area networks. In general, you should disable this option only if there are problems with databases and to isolate problems.
On
This option affects security checking for Windows clients of files with UNIX security where the requestor is not the file owner. In all cases, Windows client requests are checked against the share-level ACL. If the requestor is the owner, the User permissions determine the access.
If the requestor is not the owner and if perm_check_use_gid is On, files with UNIX security are checked using normal UNIX rules; that is, if the requestor is a member of the file's owning group, the Group permissions are used, otherwise the Other permissions are used.
blank
Specifies a second element for a single-element NetBIOS computer name. This element is case-sensitive. You use this option to isolate a group of computers on a network that communicate only with other computers with the identical NetBIOS Scope ID.
This option is not recommended if you are using DNS for name resolution because NetBIOS Scope IDs and DNS are incompatible.
For more information, refer to Microsoft documentation.
None
Specifies a list of domains that trust each other to search for a mapped account. The argument for the option is a comma-separated list that is searched in order. If no list is supplied, all domains are searched. You use this option to limit searches if you used an asterisk for a domain name in the usermap.cfg file.
FALSE
Specifies whether to show the ~snapshot snapshot directories in folders. To show the snapshot directories, set this option to TRUE.
On
If an object being accessed by a CIFS client is a symbolic link, the cifs.symlinks.cycleguard option, when set to On, eliminates the possibility of cyclic directories. It does so by preventing the following of symbolic links that contain the "dot" (".") or "dot-dot" ("..") component--symbolic links that could refer to a directory higher in the same tree. With the cifs.symlinks.cycleguard option set to Off, if you are careful, you can use symbolic links having "dot" or "dot-dot" components. For more information about this option, refer to ""How to prevent symbolic link cycling."
On
When you set cifs.symlinks.enable to On (the default setting), if the object being accessed by a CIFS client is a symbolic link, the filer follows the link with the condition that the ultimate target turns out to reside within the originating share. This ensures that the client has access permission to the target. This applies both to relative symbolic links (links to paths beginning with a character other than / and treated as a path relative to the parent directory of the symbolic link) and absolute symbolic links (links to paths beginning with / and treated as a path relative to the root of the file system). For more information about this option, refer to "Managing symbolic links for CIFS access."
Copyright © 1999, Network Appliance, Inc. All rights reserved.
Part No. 210-02334
File: options2.htm
Last updated: 04/26/99 08:12:03