version 1.16, 2009/05/29 00:16:01
|
version 1.24, 2011/01/12 13:30:19
|
|
|
platforms.<br> | platforms.<br> |
</ul> | </ul> |
| |
|
<h5>PEGASUS_EXTRA_PROVIDER_LIB_DIR</h5> |
|
<ul> |
|
<b>Description: </b>Specifies the location of the extra provider |
|
libraries which are part of the release builds.<br> |
|
<b>Default Value: </b>Not Set<br> |
|
<b>Recommended Value (Development Build): </b> |
|
No Specific Recommendation<br> |
|
<b>Recommended Value (Release Build): </b> |
|
No Specific Recommendation<br> |
|
<b>Required: </b> No.<br> |
|
<b>Considerations: </b> Since providerDir config property is fixed |
|
and hidden in release builds, this build time option provides facilty |
|
to include the extra provider directories without any security problems. |
|
This build time option is useful only when PEGASUS_OVERRIDE_DEFAULT_RELEASE_DIRS |
|
is set. |
|
</ul> |
|
|
<h5>PEGASUS_EMANATE_INCLUDE_DIR</h5> | <h5>PEGASUS_EMANATE_INCLUDE_DIR</h5> |
<ul> | <ul> |
<b>Description: </b>Specifies the location of the EMANATE | <b>Description: </b>Specifies the location of the EMANATE |
|
|
Handler to be supported.<br> | Handler to be supported.<br> |
</ul> | </ul> |
| |
|
<h5>PEGASUS_ENABLE_NET_SNMPV3</h5> |
|
<ul> |
|
<b>Description: </b>If this variable is defined, |
|
then OpenPegasus SNMP Handler will build the SNMPV3 |
|
features. This should be set to false if NET-SNMP 5.2 and lower |
|
libraries are used.<br> |
|
<b>Default Value: </b>true<br> |
|
<b>Recommended Value (Development Build): </b>true<br> |
|
<b>Recommended Value (Release Build): </b>true<br> |
|
<b>Required: </b>No<p> |
|
<b>Considerations: </b>PEGASUS_USE_NET_SNMP variable must |
|
be set.<br> |
|
</ul> |
|
|
|
|
<h5>PEGASUS_USE_OPENSLP</h5> | <h5>PEGASUS_USE_OPENSLP</h5> |
<ul> | <ul> |
<b>Description: </b>OpenSLP, <a href="http://www.openslp.org"> | <b>Description: </b>OpenSLP, <a href="http://www.openslp.org"> |
|
|
the "Release Build" configuration options. By default, | the "Release Build" configuration options. By default, |
OpenPegasus is built using the "Development Build" | OpenPegasus is built using the "Development Build" |
configuration options.<br> | configuration options.<br> |
<b>Default Value: </b>Not Set<br> |
<b>Default Value: </b>false<br> |
<b>Recommended Value (Development Build): </b>Not Set<br> |
<b>Recommended Value (Development Build): </b>false<br> |
<b>Recommended Value (Release Build): </b>Set<br> |
<b>Recommended Value (Release Build): </b>true<br> |
<b>Required: </b>No<br> | <b>Required: </b>No<br> |
<b>Considerations: </b>(1)The | <b>Considerations: </b>(1)The |
PEGASUS_USE_RELEASE_CONFIG_OPTIONS variable allows a platform | PEGASUS_USE_RELEASE_CONFIG_OPTIONS variable allows a platform |
|
|
titled "Configuration Properties" for additional detail.<br> | titled "Configuration Properties" for additional detail.<br> |
</ul> | </ul> |
| |
|
<h5>PEGASUS_FLAVOR</h5> |
|
<ul> |
|
<b>Description: </b> This variable is used for configuring Multi CIMOM |
|
on same OS by eliminating single point for storage of PID's and configuration |
|
files. Flavor is used in structuring the release dirs,configuration file names, |
|
log identity and PAM config file. |
|
If set, OpenPegasus is built using the flavor value. By default OpenPegasus is |
|
built using "tog" as the flavor. RPMs are named using the flavor value. |
|
<br> |
|
<b>Default Value: </b>tog<br> |
|
<b>Recommended Value (Development Build): </b>tog<br> |
|
<b>Recommended Value (Release Build): </b>tog<br> |
|
<b>Required: </b>No<br> |
|
<b>Considerations: </b> |
|
To build RPM using flavor, RPM spec file needs to be regenerated after setting the flavor value. |
|
This can be done using the create_OpenPegasusRPMSpecFile target in the Makefile.Release. |
|
Platforms have to define their own release dir structure using the flavor for release builds. |
|
An error will be reported if both PEGASUS_FLAVOR and PEGASUS_USE_RELEASE_DIRS are set and |
|
PEGASUS_OVERRIDE_DEFAULT_RELEASE_DIRS is not set. |
|
RPM build on linux defines PEGASUS_OVERRIDE_DEFAULT_RELEASE_DIRS by default. |
|
<br> |
|
</ul> |
|
|
|
<h5>PEGASUS_PLATFORM_FOR_32BIT_PROVIDER_SUPPORT</h5> |
|
<ul> |
|
<b>Description: </b> Builds the Pegasus with 32-bit provider support for the specified platform. |
|
If this option is set, the value MUST be one of the 32-bit supported platforms by Pegasus. |
|
<br> |
|
<b>Default Value: </b>Not set<br> |
|
<b>Recommended Value (Development Build): </b>Not set<br> |
|
<b>Recommended Value (Release Build): </b>Not set<br> |
|
<b>Required: </b>No<br> |
|
<b>Considerations: </b> |
|
This option is used to run the 32-bit providers under 64-bit CIMserver. |
|
To register the 32-bit providers, register the provider module by setting the |
|
Bitness property value to "2". 32-bit Providers are always loaded out of process |
|
irrespective of forceProviderProcesses config option. |
|
<br> |
|
</ul> |
|
|
<h5>PEGASUS_USE_SQLITE_REPOSITORY</h5> | <h5>PEGASUS_USE_SQLITE_REPOSITORY</h5> |
<ul> | <ul> |
<b>Description: </b>If true, new repository stores are created | <b>Description: </b>If true, new repository stores are created |
|
|
PEGASUS_USE_SQLITE_REPOSITORY is set to true. | PEGASUS_USE_SQLITE_REPOSITORY is set to true. |
</ul> | </ul> |
| |
|
<h5>PEGASUS_INITIAL_THREADSTACK_SIZE</h5> |
|
<ul> |
|
<b>Description: </b>This environment variable sets the initial size |
|
of the stack on new threads. Value is specified in number of bytes.<br> |
|
<b>Default Value: </b>262144<br> |
|
<b>Recommended Value (Development Build): </b>262144<br> |
|
<b>Recommended Value (Release Build): </b>262144<br> |
|
<b>Required: </b>No </p> |
|
</ul> |
|
|
<h4>Examples Building a Linux IA32 (#IA64) Development/Debug Version</h4> | <h4>Examples Building a Linux IA32 (#IA64) Development/Debug Version</h4> |
<ul> | <ul> |
export PEGASUS_ROOT=/home/pegasusbld/pegasus<br> | export PEGASUS_ROOT=/home/pegasusbld/pegasus<br> |
|
|
Pegasus/Config/SecurityPropertyOwner.cpp<p> </p> | Pegasus/Config/SecurityPropertyOwner.cpp<p> </p> |
</ul> | </ul> |
| |
<h5>enableSSLExportClientVerification</h5> |
|
<ul> |
|
<b>Description: </b>If true, the CIM Server allows HTTPS |
|
connection for CIMExport requests on the port specified by the |
|
service name "wbem-exp-https".<br> |
|
<b>Default Value: </b>false<br> |
|
<b>Recommended Default Value (Development Build): </b>true<br> |
|
<b>Recommended Default Value (Release Build): </b>false<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>No<br> |
|
<b>Source Configuration File: </b> |
|
Pegasus/Config/SecurityPropertyOwner.cpp</p> |
|
</ul> |
|
|
|
|
|
<h5>enableSubscriptionsForNonprivilegedUsers</h5> | <h5>enableSubscriptionsForNonprivilegedUsers</h5> |
<ul> | <ul> |
<b>Description: </b>If true, operations (create instance, | <b>Description: </b>If true, operations (create instance, |
|
|
Pegasus/Config/NormalizationPropertyOwner.cpp | Pegasus/Config/NormalizationPropertyOwner.cpp |
</ul> | </ul> |
| |
|
|
<h5><b>exportSSLTrustStore</b></h5> |
|
<ul> |
|
<b>Description: </b>Specifies the location of the OpenSSL |
|
truststore for Indications. Consistent with the OpenSSL |
|
implementation, a truststore can be either a file or directory. |
|
If the truststore is a directory, all the certificates within |
|
the directory are considered trusted.<br> |
|
<b>Default Value: </b>indication_trust.pem<br> |
|
<b>Recommended Default Value (Development Build): </b> |
|
indication_trust.pem<br> |
|
<b>Recommended Default Value (Release Build): </b> |
|
$CERTIFICATEDIR/indication_trust.pem<br> |
|
<b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br> |
|
<b>Recommend To Be Fixed/Hidden (Release Build): </b>Yes<br> |
|
<b>Dynamic?: </b>No<br> |
|
<b>Source Configuration File: </b> |
|
Pegasus/Config/SecurityPropertyOwner.cpp</p> |
|
</ul> |
|
|
|
<h5>forceProviderProcesses</h5> | <h5>forceProviderProcesses</h5> |
<ul> | <ul> |
<b>Description: </b>If true, the CIM Server runs Providers | <b>Description: </b>If true, the CIM Server runs Providers |
|
|
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 |