version 1.20, 2010/08/09 05:58:56
|
version 1.21, 2010/09/07 03:54:37
|
|
|
changes will apply to all new and existing connections. <br> | changes will apply to all new and existing connections. <br> |
</ul> | </ul> |
| |
|
<h5>maxFailedProviderModuleRestarts</h5> |
|
<ul> |
|
<b>Description: </b>If set to a positive integer, this value |
|
specifies the number of times the failed provider module with |
|
indications enabled are restarted automatically before being |
|
moved to Degraded state. If set to zero, failed provider module |
|
is not restarted with indications enabled automatically and |
|
will be moved to Degraded state immediately.<br> |
|
<b>Recommended Default Value (Development Build): </b>3<br> |
|
<b>Recommended Default Value (Release Build): </b>3<br> |
|
<b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br> |
|
<b>Recommend To Be Fixed/Hidden (Release Build): </b>No/No<br> |
|
<b>Dynamic?: </b>Yes<br> |
|
<b>Considerations: </b>This option controls the automatic |
|
re-enabling of the failed provider module with indications |
|
enabled. If the provider module with indications enabled fails |
|
very frequently, it affects the CIMServer normal operations because |
|
CIMServer would be busy with reloading the provider module every |
|
time it fails. This option would be helpful if the long running |
|
indication provider crashes and the management application want |
|
to receive the indications from the provider while provider fix |
|
is being delivered. In case of provider module grouping, if one of |
|
the indication provider crashes, it affects all indication providers |
|
in the provider modules of the group. Note that this is the facility |
|
provided by the CIMServer for temporary recovery of the provider and |
|
the ultimate goal SHALL be fixing the faulty provider. |
|
</ul> |
|
|
<h5>logdir</h5> | <h5>logdir</h5> |
<ul> | <ul> |
<b>Description: </b>Specifies the name of the directory | <b>Description: </b>Specifies the name of the directory |