NCP Server provides several global parameters for the SET utility that can be used to customize NCP Server for a given server. Initially, the parameters and default settings are in force, but the parameters are not explicitly added to the /etc/opt/novell/ncpserv.conf file. After you modify its default setting, an entry for the parameter and its new setting are added to the file. The parameter entry remains in the file even if you modify the setting back to the default.
IMPORTANT:If you use NCP Server in a cluster, make sure to set the same global policies on each OES 11 SP3 node in the cluster where you plan to fail over the shared volumes.
There are three methods available for modifying parameter settings:
Novell Remote Manager: You can view or modify server-level parameters by using Novell Remote Manager for Linux. Select Manage NCP Services > Manage Server, then select the Parameter Value link for the parameter in order to modify the setting. When you modify settings from Novell Remote Manager, NCP Server automatically restarts the NetIQ eDirectory daemon and the Novell NCP/NSS IPC daemon (if NSS is installed).
Command Line: You can also modify the setting from its default value by using the ncpcon set command.
ncpcon set parameter_name=value
Replace parameter_name and value with the settings you want to change. NCP Server automatically restarts the NetIQ eDirectory daemon and the Novell NCP/NSS IPC daemon (if NSS is installed). These commands are dynamic.
Edit the Configuration File: You can also modify the setting from its default value by adding the parameter to the /etc/opt/novell/ncpserv.conf file, then specifying the new value.
If you modify the /etc/opt/novell/ncpserv.conf file, you must restart the NetIQ eDirectory daemon to make the changes go into effect. For information, see Section 3.6, Restarting the NetIQ eDirectory (ndsd) Daemon.
When NSS is installed and running, and you modify values for any of the NCP Server parameters by directly editing the /etc/opt/novell/ncpserv.conf file, you must manually restart ncp2nss. For information, see Section 3.5, Restarting the Novell NCP/NSS IPC (ncp2nss) Daemon.
The following sections identify the global NCP Server parameters with their default values and valid options. For additional information about each parameter, see Section A.2, NCPCON SET Parameters.
Table 3-2 Server Parameter Information for Directory Cache Management
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
MAXIMUM_CACHED_FILES_PER_SUBDIRECTORY Controls the maximum number of file entries that can be cached by the system for a given folder in the directory cache. |
10240 |
Minimum is 512 files. |
|
MAXIMUM_CACHED_FILES_PER_VOLUME Controls the maximum number of file entries that can be cached by the system for a given volume in the directory cache. |
256000 |
Minimum is 2048 files. |
|
MAXIMUM_LAZY_CLOSE_FILES When a file is closed by the client, the NCP engine waits before closing the file just in case a client wants to reopen the file. This is called a “lazy close.” This parameter controls the maximum number of file handles that can be lazy closed in the directory cache. |
4096 |
16 to 64000 |
|
MAXIMUM_CACHED_SUBDIRECTORIES_PER_VOLUME Controls the maximum number of folder entries that can be cached by the system for a volume in the directory cache. |
102400 |
4096 |
|
LOG_CACHE_STATISTICS Controls whether cache statistics are logged in the ncpserv.log file. |
0 |
0 - Disable 1 - Enable |
For information about configuring global policies for DST, see the OES 11 SP3: Dynamic Storage Technology Administration Guide.
Table 3-3 Server Parameter Information for Dynamic Storage Technology
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
DUPLICATE_SHADOW_FILE_ACTION Controls how duplicate files conflicts are handled. |
0 |
0 - Show duplicate shadow files (default) 1 - Hide duplicate shadow files 2 - Rename duplicate shadow files 3 - Delete duplicate files from shadow area 4 - Move duplicate shadow files to /._DUPLICATE_FILES |
|
DUPLICATE_SHADOW_FILE_BROADCAST Controls whether broadcast messages are sent to NCP users whenever duplicate files conflicts occur. |
1 |
0 - Disable 1 - Enable |
|
REPLICATE_PRIMARY_TREE_TO_SHADOW Controls how the primary tree is replicated from the primary tree to the shadow tree. By default, it is disabled, and paths are replicated to the secondary storage area when data is actually moved from the primary location to the secondary location. If it is enabled, the entire tree is replicated even if no files in a path have been moved to the secondary storage location. |
0 |
0 - Disable 1 - Enable |
|
SHIFT_ACCESSED_SHADOW_FILES Controls whether files are moved from the secondary volume to the primary volume if the volume is accessed twice during a specified elapsed time. Use SHIFT_DAYS_SINCE_LAST_ACCESS to specify the time period. The file is moved after it is closed. |
0 |
0 - Disable 1 - Enable |
|
SHIFT_MODIFIED_SHADOW_FILES Controls whether files are moved from the secondary volume to the primary volume if the file is modified. The file is moved after it is closed. |
1 |
0 - Disable 1 - Enable |
|
SHIFT_DAYS_SINCE_LAST_ACCESS Specifies the number of elapsed days during which a file must be accessed twice before it is moved. This applies only if SHIFT_ACCESSED_SHADOW_FILES is enabled. |
1 |
0 - Disable 1 to 365 (in days) |
Table 3-4 Server Parameter Information for Locks Management
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
CROSS_PROTOCOL_LOCKS Controls cross-protocol file locking support with Samba. Cross-protocol locks help prevent the same file from being concurrently accessed for modifications from both a Samba and NCP client. |
1 |
1 - Enable 0 - Disable |
|
OPLOCK_SUPPORT_LEVEL Controls NCP opportunistic locking, which allows the client to cache file data for better performance. |
2 |
0 - Disable 1 - Exclusive locks 2 - Shared and exclusive locks |
|
LOCK_RANGE_MASK |
1 |
By default this parameter is turned on. Setting the parameter value to 0 turns off this parameter and does not permit locking beyond the 0x7fffffffffffffff region. |
Table 3-5 Server Parameter Information for Logging NCP Server Events
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
LOG_LEVEL Controls the nature and types of messages that are logged to the /var/opt/novell/log/ncpserv.log file. |
WARN |
Each level logs entries for its level and the levels above it.
|
|
LOG_CACHE_STATISTICS Controls whether cache statistics are logged in the ncpserv.log file. |
0 |
0 - Disable 1 - Enable |
|
LOG_IDBROKER_ERRORS Controls whether ID broker errors are logged in the ncpserv.log file. |
0 |
0 - Disable 1 - Enable |
|
LOG_MEMORY_STATISTICS Controls whether memory statistics are logged in the ncpserv.log file. |
0 |
0 - Disable 1 - Enable |
Table 3-6 Server Parameter Information for Communications
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
FIRST_WATCHDOG_PACKET Controls how long to wait in minutes of inactivity before checking to see if an NCP connection is still alive. |
0 |
0 - Disable 1-120 (minutes) - Enable |
|
DISABLE_BROADCAST Controls the ability to broadcast messages from the NCP Server. |
0 |
0 - Disable 1 - Enable |
Table 3-7 Server Parameter Information for the NCP Server Environment
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
LOCAL_CODE_PAGE Controls which base code page is used by the NCP Server. For more information, see Section 3.7, Configuring the NCP Server Local Code Page. |
CP437 |
Valid language codes |
|
NCP_FILE_SERVER_NAME This parameter is set by eDirectory when the NCP Server is installed, and must not be modified arbitrarily. For information, see Section 3.12, Modifying the NCP File Server Name. |
Server hostname |
This setting must match the server hostname, such as server1. |
Table 3-8 Server Parameter Information for Volume and File Management
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
COMMIT_FILE |
0 |
0 - Disable 1 - Enable |
|
EXECUTE_ATTRIBUTE_SUPPORT |
1 |
0 - Disable 1 - Enable |
|
KEEP_NSS_FILE_DELETOR_IDS |
1 |
0 - Disable 1 - Enable |
|
SENDFILE_SUPPORT |
0 |
0 - Disable 1 - Enable |
|
SYNC_TRUSTEES_TO_NSS_AT_VOLUME_MOUNT Controls trustee resynchronization for an NSS volume when it is mounted for NCP. |
0 |
0 - Disable 1 - Enable |
|
VOLUME_GONE_WARN_USERS Controls whether a message is broadcast to warn users when the volume path is no longer present. |
1 |
0 - Disable 1 - Enable |
Table 3-9 Server Parameter Information for Volume Low-Space Warning
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
VOLUME_EMPTY_WARN_USERS Controls whether a message is broadcast to warn users when no volume space is available. |
1 |
0 - Disable 1 - Enable |
|
VOLUME_LOW_WARN_USERS Controls whether a message is broadcast to warn users when volume space is low. |
1 |
0 - Disable 1 - Enable |
|
VOLUME_LOW_WARNING_RESET_THRESHOLD Sets the high watermark threshold (in MB), which is the level where the low watermark threshold is reset, and users no longer receive the low-space message. |
128 |
0 to 100000 |
|
VOLUME_LOW_WARNING_THRESHOLD Sets the low watermark threshold (in MB) that indicates space is low. |
64 |
0 to 100000 |
Table 3-10 Server Parameter Information for the TCP Connections
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
NCP_TCP_KEEPALIVE_INTERVAL Allows you to configure the keep-alive timeout for all TCP client connections accepted by the NCP server. The TCP keep-alive packet is sent by the server if the client is inactive for t this amount of time. This parameter also helps the NCP server to clear unwanted connections. The actual time taken to clear the unwanted NCP connections also depends on other system-wide TCP keep-alive parameters, like net.ipv4.tcp_keepalive_probes and net.ipv4.tcp_keepalive_intv. These parameters can be controlled by using the sysctl command. |
8 minutes |
Valid range: 3 minutes to 240 minutes |
|
NCP_KEEPALIVE_INTERVAL If NCP_KEEPALIVE_INTERVAL=-1, then the behavior for NCP_TCP_KEEPALIVE_INTERVAL remains unaltered. If NCP_KEEPALIVE_INTERVAL > 0, whenever the client is idle then the connections remain open till the time mentioned for this parameter elapses provided FIRST_WATCHDOG_PACKET=0 or FIRST_WATCHDOG_PACKET > NCP_KEEPALIVE_INTERVAL. |
-1 |
Valid Range: -1 and 3 minutes to 240 minutes |
Table 3-11 Server Parameter Information for the Auditing Support
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
AUDITING_SUPPORT Indicates whether auditing support is enabled for NCP. The default value is 0, which indicates that auditing is turned off. |
0 |
Valid values: 0 and 1 |
Table 3-12 Server Parameter Information for the NCP Thread
|
Parameter Name and Description |
Default Value |
Value Options |
|---|---|---|
|
ADDITIONAL_SSG_THREADS Sets the number of additional SSG Threads (above the fixed 25 NCP threads) that can be used to serve incoming NCP file service requests. These threads are used when the 25 NCP threads are busy and taking more than the expected time to finish. |
25 |
Valid range: 7 to 103 |
|
CONCURRENT_ASYNC_REQUESTS Sets the maximum number of the Async eDirectory NCP request threads that can be created. |
25 |
Valid range: 15 to 256 |