(file) Return to BuildAndReleaseOptions.html CVS log (file) (dir) Up to [Pegasus] / pegasus / doc

Diff for /pegasus/doc/BuildAndReleaseOptions.html between version 1.5 and 1.11

version 1.5, 2008/10/14 17:15:34 version 1.11, 2008/11/26 08:15:30
Line 730 
Line 730 
      indication provider.<br>      indication provider.<br>
 </ul> </ul>
  
   <h5>PEGASUS_ENABLE_PROTOCOL_INTERNAL_BINARY</h5>
   <ul>
     <b>Description: </b>If true, OpenPegasus uses a faster binary
        protocol between the CIM server and provider manager. If false,
        OpenPegasus uses the older XML-based protocol instead.
        <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<br>
     <b>Considerations: </b>This option improves performance by optimizing the
        serialization and deserialization of messages between the server and
        out-of-process providers.
        <br>
   </ul>
   
   <h5>PEGASUS_ENABLE_PROTOCOL_BINARY</h5>
   <ul>
     <b>Description: </b>If true, OpenPegasus uses a faster binary
        protocol between local clients (including the provider agent) and the
        CIM server. If false, OpenPegasus uses the conventional XML-based protocol
        instead. See PEP#340 for more details.
        <br>
     <b>Default Value: </b>false<br>
     <b>Recommended Value (Development Build): </b>false<br>
     <b>Recommended Value (Release Build): </b>false<br>
     <b>Required: </b>No<br>
     <b>Considerations: </b>This option improves performance by using a faster
        binary protocol between local clients and the CIM server.
        <br>
   </ul>
   
 <h5>PEGASUS_ENABLE_INTEROP_PROVIDER</h5> <h5>PEGASUS_ENABLE_INTEROP_PROVIDER</h5>
 <ul> <ul>
   <b>Description: </b>If true, the OpenPegasus Interop Provider   <b>Description: </b>If true, the OpenPegasus Interop Provider
Line 1658 
Line 1690 
      titled "Configuration Properties" for additional detail.<br>      titled "Configuration Properties" for additional detail.<br>
 </ul> </ul>
  
   <h5>PEGASUS_USE_SQLITE_REPOSITORY</h5>
   <ul>
     <b>Description:&nbsp;</b>If true, new repository stores are created
        using a SQLite database.  Existing file-based stores will continue
        to be recognized and operate seamlessly.<br>
     <b>Default Value:&nbsp;</b>false<br>
     <b>Recommended Value (Development Build):&nbsp;</b>true<br>
     <b>Recommended Value (Release Build):&nbsp;</b>true<br>
     <b>Required:&nbsp;</b>No<br>
     <b>Considerations:&nbsp;</b>If PEGASUS_USE_SQLITE_REPOSITORY is set to true
        and SQLite files are not installed in default search locations,
        SQLITE_HOME must also be configured.
        PEGASUS_REPOSITORY_STORE_COMPLETE_CLASSES may not be set to true when
        PEGASUS_USE_SQLITE_REPOSITORY is set to true.
   </ul>
   
 <h5>PEGASUS_USE_SYSLOGS</h5> <h5>PEGASUS_USE_SYSLOGS</h5>
 <ul> <ul>
   <b>Description:&nbsp;</b>If set, OpenPegasus will be built   <b>Description:&nbsp;</b>If set, OpenPegasus will be built
Line 1688 
Line 1736 
      compiler version &lt; 1300.<br>      compiler version &lt; 1300.<br>
 </ul> </ul>
  
   <h5>SQLITE_HOME</h5>
   <ul>
     <b>Description:&nbsp;</b>Specifies the location of the SQLite SDK directory.
        This directory must contain sqlite3.h in the $(SQLITE_HOME)/include
        directory, and libsqlite3 in the $(SQLITE_HOME)/lib directory.<br>
     <b>Default Value:&nbsp;</b>Not Set<br>
     <b>Recommended Value (Development Build):&nbsp;</b>
        No Specific Recommendation<br>
     <b>Recommended Value (Release Build):&nbsp;</b>
        No Specific Recommendation<br>
     <b>Required:&nbsp;</b>Yes, if PEGASUS_USE_SQLITE_REPOSITORY is set to true
        and the SQLite files are not installed in locations that are searched by
        default.<br>
     <b>Considerations:&nbsp;</b>This environment variable is only used if
        PEGASUS_USE_SQLITE_REPOSITORY is set to true.
   </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>
Line 2160 
Line 2225 
   <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>   <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
   <b>Dynamic?:&nbsp;</b>No<br>    <b>Dynamic?:&nbsp;</b>Yes<br>
   <b>Considerations:&nbsp;</b>   <b>Considerations:&nbsp;</b>
     <ul>     <ul>
       <li>Any errors encountered during normalization result in a       <li>Any errors encountered during normalization result in a
Line 2504 
Line 2569 
   <b>Recommended Default Value (Release Build):&nbsp;</b>0<br>   <b>Recommended Default Value (Release Build):&nbsp;</b>0<br>
   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
     <b>Dynamic?:&nbsp;</b>Yes<br>
   <b>Considerations:&nbsp;</b>A client connection is considered   <b>Considerations:&nbsp;</b>A client connection is considered
      idle when it is not in the process of sending a request and      idle when it is not in the process of sending a request and
      the CIM Server is not processing a request from that connection.      the CIM Server is not processing a request from that connection.
Line 2516 
Line 2582 
      considered when configuring an idle connection timeout value.      considered when configuring an idle connection timeout value.
      The idle connection time is computed using the system clock.      The idle connection time is computed using the system clock.
      Thus, resetting the system clock may cause unexpected timeout      Thus, resetting the system clock may cause unexpected timeout
      behavior.<br>       behavior.This config property can be changed dynamically. The
        changes will apply to all new and existing connections. <br>
 </ul> </ul>
  
 <h5>logdir</h5> <h5>logdir</h5>
Line 2575 
Line 2642 
   <b>Recommended Default Value (Release Build):</b>&nbsp;0<br>   <b>Recommended Default Value (Release Build):</b>&nbsp;0<br>
   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
   <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/Yes<br>   <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/Yes<br>
   <b>Dynamic?:&nbsp;</b>No<br>    <b>Dynamic?:&nbsp;</b>Yes<br>
   <b>Considerations:&nbsp;</b><br>    <b>Considerations:&nbsp;</b>Consider there are five provider processes
        already running and the maxProviderProcesses is dynamically changed to
        four. In this case though new provider processes will not be created
        but existing five will continue running<br>
      <br>      <br>
      <table border="1" cellspacing="1" bordercolordark="#666666"      <table border="1" cellspacing="1" bordercolordark="#666666"
          bordercolorlight="#CCCCCC" width=531          bordercolorlight="#CCCCCC" width=531
Line 2630 
Line 2700 
      $PROVIDERDIRS<br>      $PROVIDERDIRS<br>
   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
   <b>Dynamic?:&nbsp;</b>No<br>    <b>Dynamic?:&nbsp;</b>Yes<br>
   <b>Considerations:&nbsp;</b>The CIM Server runs as a privileged   <b>Considerations:&nbsp;</b>The CIM Server runs as a privileged
      user. And, since Providers run in the same process space as the      user. And, since Providers run in the same process space as the
      CIM Server, Providers also have privileged access to the      CIM Server, Providers also have privileged access to the
Line 2822 
Line 2892 
      20 (seconds)<br>      20 (seconds)<br>
   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>   <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
   <b>Dynamic?:&nbsp;</b>No<br>    <b>Dynamic?:&nbsp;</b>Yes<br>
     <b>Considerations:&nbsp;</b>Any changes made to this config property
        dynamically will apply to new CIM Server connections only
        keeping old already established connections unchanged.<br>
   <b>Source Configuration File:&nbsp;</b>   <b>Source Configuration File:&nbsp;</b>
      Pegasus/Config/DefaultPropertyTable.h      Pegasus/Config/DefaultPropertyTable.h
 </ul> </ul>


Legend:
Removed from v.1.5  
changed lines
  Added in v.1.11

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2