You can manager the NFS Gateway parameters using either iManager or the command line.
The NFS Gateway Properties page lets you view and edit the NFS Gateway general and log parameters.
For details, see Section 7.2.4, Viewing and Modifying the NFS Gateway Parameters.
Use the following syntax at the command line to set the NFS Gateway parameters. These parameters apply to the NFS Gateway volumes mounted on the system.
nfsgy [-shadowCacheSize value][-pageCacheSize value] [-shadowVolume volumeName][-logFileSize value][-logLevel value][-logVerbose] [-logFlushImmediate]
The NFS Gateway supports dynamic configuration for certain parameters. This means that the changes made in these parameters are taken into effect automatically and there is no need to restart NFS Gateway for the changed parameters to take effect.
The following table describes the parameters. It also gives the default value and the valid range and mentions if dynamic configuration is supported for that parameter.
|
Parameter |
Default |
Description |
Dynamic Configuration Support |
|---|---|---|---|
|
shadowCacheSize |
8 |
Size of the shadow cache (in MB). Range = 8 to 32 For improved performance, we recommend that you set the value to 32 MB. |
Yes Can only be increased. |
|
pageCacheSize |
8 |
Size of the page cache (in MB). Range = 8 to system limit The maximum limit is based on the available system memory. For example, 8 MB of page cache size is adequate to hold up to 50,000 entries in a single directory. If the number of entries in a single directory is greater than 50,000, we recommend that you increase the pageCacheSize value. |
Yes Can only be increased |
|
shadowVolume |
sys: |
Specifies the name of the volume where shadow files are to be stored. The shadow files are stored in shadowVolume:\gateway directory. The shadow volume specified with the nfsgy command is used if the shadowVolume parameter is not specified with the gymount command. The NFS Gateway does not load if the specified volume is not available. Do not use the mounted Gateway volumes as ShadowVolume when mounting another volume using gymount. For example, if vol1 is a mounted NFS Gateway volume, then do not execute the following: gymount vol2 -shadowvolume vol1 When shadowVolume is not using the default of sys: and if the trustee information is lost when using a gateway volume in a cluster enabled environment, or using a newly mounted NSS volume as shadowVolume, then in the Section 11.0, Troubleshooting the NFS Gateway for NetWare 6.5 chapter, refer to the troubleshooting scenario. IMPORTANT:Do not dismount or deactivate the volume that shadowVolume points to when the NFS Gateway is loaded. Doing so results in deactivation of volumes imported by the NFS Gateway. |
No |
|
logFileSize |
4 MB |
Specifies the log file size (in MB). The maximum value can be 32 MB. If any invalid value is specified, then the default value is used. After the log file size reaches the set value, the contents of the log file (.log) file are backed up as the .bak file. The log messages specific to each volumes are saved as shadowVolume/gateway/volumename.log. The general log messages for the NFS Gateway are saved as shadowVolume/gateway/system.log. |
No |
|
logLevel |
1 |
Specifies the logging level to be enabled for the volume. 0, 1, 2, 4, and 8 are the valid log levels. The values indicate the following: 0 = None (Logging is disabled) 1 = Errors 2 = Warning , Errors 4 = Info, Warning, and Errors 8 = Debug, Info, Warning, and Errors The logLevel = 8 is not recommended in typical cases. Use this only for debugging purposes. |
Yes |
|
logVerbose |
Disabled |
Specifies the log verbose information. |
Yes |
|
logFlushImmediate |
Disabled |
If specified, forces the log messages to be written to file immediately. If not set, the log messages are cached until the buffer is full. |
No |