Setting the optional base daemon behavior parameters
The
daemon_options file contains a set of parameters that can be modified to affect base daemon behavior. The file contains editable behavior parameters set to certain optional defaults in the line entries. Commented lines beginning with a pound sign (#) are ignored.
To remove any parameter option, remove the line entry, rename the file, or comment the line by adding a pound sign (#) at the beginning of the line entry.
Table 1 lists some of the possible optional base daemon parameters.
Specifies how long (in seconds) inquiry results are to remain in cache before expiring, and new data retrieved from the host and array. A value of
-1 indicates the data never expires. A value of zero indicates the data always expires.
storapid:gk_use
dedicated_only |
legacy
Specifies whether the base daemon is restricted to only using dedicated gatekeeper devices when making syscalls.
dedicated_only restricts the base daemon to only dedicated gatekeepers.
legacy allows the base daemon to use non-dedicated gatekeeper devices.
storapid:use_all_gks
disabled |
enabled
Specifies whether the base daemon is free to use all available gatekeeper candidates.
disabled restricts the base daemon to using only 75% of the available gatekeeper candidates. This option locks the gatekeeper with a host-based lock, such as a semaphore or mutex.
enabled allows the base daemon to use all available gatekeeper candidates. This option locks the gatekeeper with an internal locking mechanism.
If you are running InfoMover, you must set this option to
disabled.
aFor more information on the available parameters, refer to the
daemon_options
file.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\