From: Joshua Slive Date: Fri, 10 Aug 2001 15:58:16 +0000 (+0000) Subject: Eliminate duplicate info and add references to logs.html. X-Git-Tag: 2.0.24~129 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=885ffa294e3341e79928580ac5821291559c185c;p=apache Eliminate duplicate info and add references to logs.html. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@90068 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/configuring.html.en b/docs/manual/configuring.html.en index f626637083..ea87f8a9f3 100644 --- a/docs/manual/configuring.html.en +++ b/docs/manual/configuring.html.en @@ -21,7 +21,6 @@
  • Modules
  • Scope of Directives
  • .htaccess Files
    • -
  • Log Files
    • @@ -196,53 +195,6 @@ configuring the AllowOverride directive in the main configuration files. -
    - -

    Log files

    - -

    security warning

    -Anyone who can write to the directory where Apache is writing a -log file can almost certainly gain access to the uid that the server is -started as, which is normally root. Do NOT give people write -access to the directory the logs are stored in without being aware of -the consequences; see the security tips -document for details. - -

    pid file

    - -

    On startup, Apache saves the process id of the parent httpd process to -the file logs/httpd.pid. This filename can be changed -with the PidFile directive. The -process-id is for use by the administrator in restarting and -terminating the daemon: on Unix, a HUP or USR1 signal causes the -daemon to re-read its configuration files and a TERM signal causes it -to die gracefully; on Windows, use the -k command line option instead. -For more information see the Stopping and -Restarting page. - -

    -If the process dies (or is killed) abnormally, then it will be necessary to -kill the children httpd processes. - -

    Error log

    - -

    The server will log error messages to a log file, by default -logs/error_log on Unix or logs/error.log on -Windows and OS/2. The filename can be set using the ErrorLog directive; different error -logs can be set for different virtual hosts. - -

    Transfer log

    - -

    The server will typically log each request to a transfer file, by -default logs/access_log on Unix or -logs/access.log on Windows and OS/2. The filename can be -set using a CustomLog -directive; different transfer logs can be set for different virtual hosts. - - diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index f3dad52e29..f4041e9f8b 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -747,7 +747,8 @@ document for details on why your security could be compromised if the directory where logfiles are stored is writable by anyone other than the user that starts the server. -

    See also: LogLevel +

    See also: LogLevel and +Apache Log Files

    <Files> directive

    diff --git a/docs/manual/mod/mod_log_config.html b/docs/manual/mod/mod_log_config.html index c007eb7281..7070deb55c 100644 --- a/docs/manual/mod/mod_log_config.html +++ b/docs/manual/mod/mod_log_config.html @@ -53,6 +53,8 @@ be used multiple times in each server to cause each request to be logged to multiple files.

    +

    See also: Apache Log Files.

    +

    Directives

    -

    Log File Formats

    - -

    Unless told otherwise with LogFormat, the log files -created by TransferLog will be in standard "Common Log -Format" (CLF). The contents of each line in a CLF file are explained -below. Alternatively, the log file can be customized (and if multiple -log files are used, each can have a different format). Custom formats -are set with LogFormat and CustomLog.

    - -

    Common Log Format

    - -

    The Common Log Format (CLF) file contains a separate line for each -request. A line is composed of several tokens separated by spaces:

    - -
    -host ident authuser date request status bytes -
    -If a token does not have a value then it is represented by a hyphen (-). -The meanings and values of these tokens are as follows: -
    -
    host -
    The fully-qualified domain name of the client, or its IP number if the -name is not available. -
    ident -
    If IdentityCheck is enabled and the -client machine runs identd, then this is the identity information reported -by the client. -
    authuser -
    If the request was for an password protected document, then this is -the userid used in the request. -
    date -
    The date and time of the request, in the following format: -
    date = [day/month/year:hour:minute:second zone]
    -day = 2*digit
    -month = 3*letter
    -year = 4*digit
    -hour = 2*digit
    -minute = 2*digit
    -second = 2*digit
    -zone = (`+' | `-') 4*digit
    -
    request -
    The request line from the client, enclosed in double quotes -("). -
    status -
    The three digit status code returned to the client. -
    bytes -
    The number of bytes in the object returned to the client, not including -any headers. -
    - -

    Custom Log Formats

    +

    Custom Log Formats

    The format argument to the LogFormat and CustomLog directives is a string. This string is logged @@ -210,24 +162,6 @@ otherwise log analysis programs would have to duplicate the entire vhost matching algorithm in order to decide what host really served the request.

    -

    Using Multiple Log Files

    - -

    The TransferLog and CustomLog directives can -be given more than once to log requests to multiple log files. Unless -the conditional form of CustomLog is used, each -request will be logged to all the log files defined by either of these -directives.

    - -

    Use with Virtual Hosts

    - -

    If a <VirtualHost> section does not contain any -TransferLog or CustomLog directives, the -logs defined for the main server will be used. If it does -contain one or more of these directives, requests serviced by -this virtual host will only be logged in the log files defined -within its definition, not in any of the main server's log files. -See the examples below.

    -

    Security Considerations

    See the security tips @@ -235,30 +169,6 @@ document for details on why your security could be compromised if the directory where logfiles are stored is writable by anyone other than the user that starts the server.

    -

    Resetting the Log Files

    - -

    The access log file typically grows 1MB or more for each 10,000 -requests. It will probably be necessary to move or delete the log -file on a regular basis. This cannot be done while the server is -still running, because Apache will continue writing to the old log -file. Instead, the server must be restarted after the log file is moved or -deleted so that it will open a new log.

    - -

    A typical scenario is:

    - -
    -   mv access_log access_log.old
-   apachectl graceful
-   # wait for all requests to the old server to complete
-   # before doing anything with access_log.old
-
    - -

    Alternatively, log files can be rotated automatically be writing -them through a pipe to a program designed for that purpose such -as rotatelogs.

    -