A while ago we started discussing ways to streamline and clean-up the 2.0
FAQ.  I've been busy in the interim, but I finally found a few minutes to
take a look at this.  Below is a sketch for the structure of the new FAQ.
Only the main page and the "support" page are implemented. The important
points are

1. By default, each category is accessed under its own page.
2. By tagging "?ONEPAGE" onto the end of the URL of the main page, you can
get an all-in-one-page version.

I tried hard to keep things simple, and to make sure that you could still
navigate the FAQ even if SSI was turned off.  (You will get two copies of
the category index, and only the top one will work.)

So I am interested in hearing if this meets people's needs for basic
structure, and if anyone has suggestions for structural/SSI code
improvement.

If the basic structure is approved, the next steps are
1. Determining which categories to use.
2. Determining which questions should be brought over from the 1.3 FAQ.

The rendered version of the FAQ (SSI processed) is available at
http://garibaldi.commerce.ubc.ca:8080/ap20/manual/FAQ/

-- 
Joshua Slive
[EMAIL PROTECTED]
http://slive.ca/
Phone: (604) 822-1871
Title: Support - Apache Server Frequently Asked Questions

Apache Server 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/apache/logs/error_log, but see the ErrorLog directive in your config files for the location on your server.

  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. 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. Ask in the comp.infosystems.www.servers.unix or comp.infosystems.www.servers.ms-windows USENET newsgroup (as appropriate for the platform you use).

    A lot of common problems never make it to the bug database because there's already high Q&A traffic about them in the comp.infosystems.www.servers.unix newsgroup. Many Apache users, and some of the developers, can be found roaming its virtual halls, so it is suggested that you seek wisdom there. The chances are good that you'll get a faster answer there than from the bug database, even if you don't see your question already posted.

  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.)


Whom do I contact for support?

There is no official support for Apache. None of the developers want to be swamped by a flood of trivial questions that can be resolved elsewhere. Bug reports and suggestions should be sent via the bug report page. Other questions should be directed to the comp.infosystems.www.servers.unix or comp.infosystems.www.servers.ms-windows newsgroup (as appropriate for the platform you use), where some of the Apache team lurk, in the company of many other httpd gurus who should be able to help.

Commercial support for Apache is, however, available from a number of third parties.

Title: 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?
Building Apache
Why won't Apache compile?
Starting Apache
Why won't Apache start?
Error Messages
What does this error mean?
Support
What do I do when I have problems?
Building Apache
Why won't Apache compile?
Starting Apache
Why won't Apache start?
Error Messages
What does this error mean?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to