 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
With logging enabled, the Web server appends relevant data to the current-httpd.log file at the end of each request. The current-httpd.log file is located in the directory that was specified by the LogFileDirectorysetting. Each log entry contains the date and time of the request, the IP address of the client, the method that was used, the URL that was requested, the response code that was sent back, and, optionally, data that was appended by ISAPI extensions, ISAPI filters, or the ASP page.
When the size of the current-httpd.log file approaches the size that is specified in the MaxLogSizeregistry value, the logging process renames it to "previous-httpd.log" and creates a new file that is named "current-httpd.log". If a file that is named "previous-httpd.log" existed before this rollover occurred, that file is overwritten.
Note that if you set the logging to an invalid directory, but do not set the MaxLogSizeregistry value to 0, it can take 15 additional seconds for the Web server to begin accepting connections. If the Web server cannot create the log file, it does not abandon logging immediately, but attempts to reopen the log file once every second for 15 seconds. This functionality has been added because it is possible that the log file is being set up on a flash device that was not initialized by the time that the Web server starts up during the startup sequence.
Therefore, if you do not want to perform logging, it is recommended that you set the MaxLogSizeregistry value to 0 to avoid this delay.
Last updated on Friday, April 02, 2004