mod_info/3656: mod_info gripes about non-existent srm.conf / access.conf

[Eric Cholet <ch...@logilune.com>]

>Number:         3656
>Category:       mod_info
>Synopsis:       mod_info gripes about non-existent srm.conf / access.conf
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jan 13 07:30:02 PST 1999
>Last-Modified:
>Originator:     cholet@logilune.com
>Organization:
apache
>Release:        1.3.4
>Environment:
FreeBSD 2.2.7-RELEASE
gcc version 2.7.2.1
>Description:
1.3.4 claims to use unified configuration file httpd.conf. However mod_info still
looks for srm.conf and access.conf:

GET /server-info yields these errors

httpd: [Tue Jan 12 22:12:14 1999] [warn] [client 192.168.1.2] (2)No such file or directory: mod_info: couldn't open config file /usr/local/www/conf/srm.conf
httpd: [Tue Jan 12 22:12:14 1999] [warn] [client 192.168.1.2] (2)No such file or directory: mod_info: couldn't open config file /usr/local/www/conf/access.conf

>How-To-Repeat:
Do not specify AccessConfig or ResourceConfig statements in httpd.conf.
Compile Apache with mod_info, and access the mod_info handler.
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@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!         ]