www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brad Cox <b...@gmu.edu>
Subject general/3285: Configuration files in etc versus conf?
Date Sat, 24 Oct 1998 17:49:45 GMT

>Number:         3285
>Category:       general
>Synopsis:       Configuration files in etc versus conf?
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Oct 24 10:50:00 PDT 1998
>Originator:     bcox@gmu.edu
>Release:        1.3.3
Linux vs2 2.0.30 #1 Sun Jul 19 14:49:01 EDT 1998 i586 unknown
Sometimes apache reads config files from PREFIX/etc, other times from PREFIX/conf. I think
this is caused by different assumptions made by the apaci configuration script and the manual
configuration procedure in PREFIX/src. I got that impression from comparing the READMEs in
the two locations, which describe different conventions... etc in one place, conf in the other.
Compare the dox in the two locations re: etc vs conf
Settle on one or the other, or document why two conventions are useful.
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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