From: Rich Bowen Date: Sat, 22 Sep 2001 19:14:10 +0000 (+0000) Subject: Ran w3c tidy to convert to xhtml X-Git-Tag: 2.0.26~197 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a925e51e850a8d4ea6a0a9e8625964d2bc0d9d22;p=thirdparty%2Fapache%2Fhttpd.git Ran w3c tidy to convert to xhtml git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91114 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/faq/footer.html b/docs/manual/faq/footer.html index 4a0991e6fa3..edcc022ccc5 100644 --- a/docs/manual/faq/footer.html +++ b/docs/manual/faq/footer.html @@ -1,8 +1,19 @@ -
+ -

- Apache HTTP Server Version 2.0 -

+ + + + + + + + +
+ +

Apache HTTP Server Version 2.0

+ Index + Home + + -Index -Home diff --git a/docs/manual/faq/header.html b/docs/manual/faq/header.html index 9bc11593a33..6c4764044e6 100644 --- a/docs/manual/faq/header.html +++ b/docs/manual/faq/header.html @@ -1,6 +1,19 @@ -
- [APACHE DOCUMENTATION] -

- Apache HTTP Server Version 2.0 -

-
+ + + + + + + + + + +
+ [APACHE DOCUMENTATION] + +

Apache HTTP Server Version 2.0

+
+ + + diff --git a/docs/manual/faq/index.html b/docs/manual/faq/index.html index 90c19b7bb96..5916e759689 100644 --- a/docs/manual/faq/index.html +++ b/docs/manual/faq/index.html @@ -1,67 +1,58 @@ - + - + - - - - Apache Server Frequently Asked Questions - - - -

Frequently Asked Questions

+ + + + + + + Apache Server Frequently Asked Questions + + + + + +

Frequently Asked Questions

+ +

The latest version of this FAQ is always available from the + main Apache web site, at <http://httpd.apache.org/docs-2.0/faq/>. + In addition, you can view this FAQ + all in one page for easy searching and + printing. +

+ +

Since Apache 2.0 is very new, we don't yet know what the + Frequently Asked Questions will be. While this section + fills up, you should also consult the Apache 1.3 + FAQ to see if your question is answered there.

+ +

Categories

+ + +
+
Support
+ +
What do I do when I have problems?
+
+ + +
+
Support
+ +
What do I do when I have problems?
+
+
+ + + + + -

- The latest version of this FAQ is always available from the main - Apache web site, at <http://httpd.apache.org/docs-2.0/faq/>. - In addition, you can view this FAQ all in one page for easy searching and - printing. -

- -

Since Apache 2.0 is very new, we don't yet know what the - Frequently Asked Questions will be. While this section - fills up, you should also consult the Apache 1.3 FAQ - to see if your question is answered there.

- - - -

Categories

- - - -
- -
Support
-
What do I do when I have problems?
- -
- - - -
- -
Support
-
What do I do when I have problems?
- -
- -
- - - - - - - - diff --git a/docs/manual/faq/support.html b/docs/manual/faq/support.html index b72aeb790a8..25e93df208b 100644 --- a/docs/manual/faq/support.html +++ b/docs/manual/faq/support.html @@ -1,146 +1,164 @@ - - - - Support - Apache Server Frequently Asked Questions - - - - -

Frequently Asked Questions

- - -

Support

- - - -
- -

"Why can't I ...? Why won't ... work?" - What to do in case of problems

-

- If you are having trouble with your Apache server software, you should - take the following steps: -

-
    -
  1. Check the errorlog! -

    - Apache tries to be helpful when it encounters a problem. In many - cases, it will provide some details by writing one or messages to - the server error log. Sometimes this is enough for you to diagnose - & fix the problem yourself (such as file permissions or the like). - The default location of the error log is - /usr/local/apache2/logs/error_log, but see the - ErrorLog - directive in your config files for the location on your server. -

    -
    2. -
  2. Check the - FAQ! -

    - The latest version of the Apache Frequently-Asked Questions list can - always be found at the main Apache web site. -

    -
    3. -
  3. Check the Apache bug database -

    - Most problems that get reported to The Apache Group are recorded in - the - bug database. - Please check the existing reports, open - and closed, before adding one. If you find - that your issue has already been reported, please don't add - a "me, too" report. If the original report isn't closed - yet, we suggest that you check it periodically. You might also - consider contacting the original submitter, because there may be an - email exchange going on about the issue that isn't getting recorded - in the database. -

    -
    4. -
  4. Ask in a user support forum -

    Apache has an active community of users who are willing to - share their knowledge. Participating in this community is - usually the best and fastest way to get answers to your - questions and problems.

    -

    USENET newsgroups:

    -
      -
    • comp.infosystems.www.servers.unix - [nntp] - [google] -
      • -
    • comp.infosystems.www.servers.ms-windows - [nntp] - [google] -
      • -
    • comp.infosystems.www.authoring.cgi - [news] - [google] -
      • -
    - -

    Mailing Lists:

    - -
    5. -
  5. If all else fails, report the problem in the bug - database -

    - If you've gone through those steps above that are appropriate and - have obtained no relief, then please do let The Apache - Group know about the problem by - logging a bug report. -

    -

    - If your problem involves the server crashing and generating a core - dump, please include a backtrace (if possible). As an example, -

    -

    -

    -
    # cd ServerRoot
    - # dbx httpd core
    - (dbx) where     -
    -
    -

    -

    - (Substitute the appropriate locations for your - ServerRoot and your httpd and - core files. You may have to use gdb - instead of dbx.) -

    -
    6. -
-
- -

Whom do I contact for support?

- -

With several million users and fewer than forty volunteer - developers, we cannot provide personal support for Apache. For free - support, we suggest participating in a user - forum.

- -

Professional, commercial support for Apache is available from - a number of - companies.

+ - + + + + + Support - Apache Server Frequently Asked + Questions + + + + + + +

Frequently Asked Questions

+ + +

Support

+ + +
+ +

"Why can't I ...? Why won't + ... work?" What to do in case of problems

+ +

If you are having trouble with your Apache server software, + you should take the following steps:

+ +
    +
  1. + Check the errorlog! + +

    Apache tries to be helpful when it encounters a problem. + In many cases, it will provide some details by writing one + or messages to the server error log. Sometimes this is + enough for you to diagnose & fix the problem yourself + (such as file permissions or the like). The default + location of the error log is + /usr/local/apache2/logs/error_log, but see the + ErrorLog + directive in your config files for the location on your + server.

    +
    2. + +
  2. + Check the FAQ! + + +

    The latest version of the Apache Frequently-Asked + Questions list can always be found at the main Apache web + site.

    +
    3. + +
  3. + Check the Apache bug database + +

    Most problems that get reported to The Apache Group are + recorded in the bug + database. Please check the + existing reports, open and closed, before + adding one. If you find that your issue has already + been reported, please don't add a "me, too" + report. If the original report isn't closed yet, we suggest + that you check it periodically. You might also consider + contacting the original submitter, because there may be an + email exchange going on about the issue that isn't getting + recorded in the database.

    +
    4. + +
  4. + Ask in a + user support forum + +

    Apache has an active community of users who are willing + to share their knowledge. Participating in this community + is usually the best and fastest way to get answers to your + questions and problems.

    + +

    USENET newsgroups:

    + + + +

    Mailing Lists:

    + + +
    5. + +
  5. + If all else fails, report the problem in the bug + database + +

    If you've gone through those steps above that are + appropriate and have obtained no relief, then please + do let The Apache Group know about the problem by + logging a + bug report.

    + +

    If your problem involves the server crashing and + generating a core dump, please include a backtrace (if + possible). As an example,

    + +
    +
    # cd ServerRoot
    + # dbx httpd core
    + (dbx) where
    +
    + +

    (Substitute the appropriate locations for your + ServerRoot and your httpd and + core files. You may have to use + gdb instead of dbx.)

    +
    6. +
+
+ +

Whom do I contact for + support?

+ +

With several million users and fewer than forty volunteer + developers, we cannot provide personal support for Apache. For + free support, we suggest participating in a user forum.

+ +

Professional, commercial support for Apache is available + from a number + of companies.

+ + + + + - - - -