www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joshua Slive <sl...@finance.commerce.ubc.ca>
Subject documentation/6033: possible error in mod_status documentation
Date Thu, 27 Apr 2000 21:07:07 GMT

>Number:         6033
>Category:       documentation
>Synopsis:       possible error in mod_status documentation
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Apr 27 14:10:01 PDT 2000
>Originator:     slive@finance.commerce.ubc.ca
>Release:        1.3.12
Someone who understands mod_status should probably take a look at                        
The documentation refers to a compile-time change to activate                   
enhanced status logging.  I believe that this has been replaced                 
by the runtime directive ExtendStatus.  If so, the documentation                
is incorrect and should be changed.                                             


 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message