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

Diff for /pegasus/doc/BuildAndReleaseOptions.html between version 1.13 and 1.15

version 1.13, 2008/12/18 16:41:52 version 1.15, 2009/05/27 05:56:21
Line 2170 
Line 2170 
   <b>Recommended Default Value (Release Build):&nbsp;</b>true<br>   <b>Recommended Default Value (Release Build):&nbsp;</b>true<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<p>&nbsp;<br>    <b>Dynamic?:&nbsp;</b>Yes/No<br>
     <b>Considerations:&nbsp;</b>When enableIndicationService is set to
        false dynamically, delete subscription requests are sent to all
        indication providers and indication related operations are
        not supported until indication service is re-enabled. Dynamic
        configuration facility is available only when Pegasus is compiled
        with PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT=true. Clients
        who wants to utilize the IndicationService services MUST check for
        CIM_IndicationService EnabledState and HealthState properties to know
        the current indication service state. For example, User can enumerate
        instances of CIM_IndicationService and there is exactly one instance
        of CIM_IndicationService returned. (Ex. using cimcli command
        'cimcli ei -n root/PG_InterOp CIM_IndicationService'). When requested state
        change(Enabled/Disabled) cannot be made because of timeout or some
        other exception IndicationService HealthState is set to "Degraded/Warning".
        For example, if user requested for indication service disable (by setting
        enableIndicationService=false), disable failed because of timeout or some
        other exception. Now service health state is set to "Degraded/Warning"
        and service EnabledState will remain enabled. User can now identify the
        faulty provider causing the timeout or any other problem and can take
        appropriate action. User can again request for service disable to recover
        from degraded state. Similar sequence applies while enabling the indication
        service. Only difference is that service EnabledState is set to Enabled
        if exception or timeout happens. There is no automatic recovery from
        degraded state is available at present.<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 3033 
Line 3057 
 <ul> <ul>
   <b>Description:&nbsp;</b>Defines the desired facility for trace   <b>Description:&nbsp;</b>Defines the desired facility for trace
      messages. Valid values include: &quot;File&quot;      messages. Valid values include: &quot;File&quot;
      and &quot;Log&quot;.<br>       , &quot;Log&quot; and &quot;Memory&quot; .<br>
   <b>Default Value:&nbsp;</b>File<br>   <b>Default Value:&nbsp;</b>File<br>
   <b>Recommended Default Value (Development Build): </b>File<br>   <b>Recommended Default Value (Development Build): </b>File<br>
   <b>Recommended Default Value (Release Build): </b>File<br>   <b>Recommended Default Value (Release Build): </b>File<br>
Line 3045 
Line 3069 
      trace messagesare written into the file specified by the      trace messagesare written into the file specified by the
      configuration option traceFilePath. If you specify      configuration option traceFilePath. If you specify
      &quot;Log&quot;, trace messages are written to the      &quot;Log&quot;, trace messages are written to the
      OpenPegasus Log.<br>       OpenPegasus Log. If you specify Memory, the trace messages
        are collected in a wrap-around memory buffer.
        If this memory is part of a dump the trace messages can be
        found by the eye-catcher &quot;PEGASUSMEMTRACE&quot; at
        the top of the memory buffer. The trace is in clear text and
        the last written message has the suffix &quot;EOTRACE&quot;.<br>
   <b>Source Configuration File:&nbsp;</b>   <b>Source Configuration File:&nbsp;</b>
      Pegasus/Config/TracePropertyOwner.cpp<br>      Pegasus/Config/TracePropertyOwner.cpp<br>
 </ul> </ul>
Line 3080 
Line 3109 
      Pegasus/Config/TracePropertyOwner.cpp<br>      Pegasus/Config/TracePropertyOwner.cpp<br>
 </ul> </ul>
  
   <h5>traceMemoryBufferKbytes</h5>
   <ul>
     <b>Description:&nbsp;</b>Defines the size of the buffer for
       in memory tracing in kbytes ( 2<sup>10</sup> bytes ).
       Smallest value is 16.<br>
     <b>Default Value:&nbsp;</b>10240<br>
     <b>Recommended Default Value (Development Build): </b>10240<br>
     <b>Recommended Default Value (Release Build): </b>10240<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?:&nbsp;</b>No<br>
     <b>Case Sensitive?:&nbsp;</b>No<br>
     <b>Considerations:&nbsp;</b>Is ignored if configuration
       property traceFacility is not set to Memory.<br>
     <b>Source Configuration File:&nbsp;</b>
        Pegasus/Config/TracePropertyOwner.cpp<br>
   </ul>
   
 <h3>Configuration Constants</h3> <h3>Configuration Constants</h3>
  
 <h4>Definitions</h4> <h4>Definitions</h4>

Legend:
Removed from v.1.13  
changed lines
  Added in v.1.15
No CVS admin address has been configured
 Powered by
ViewCVS 0.9.2