Bug 23239 - Problem with httpd.conf supplied
Problem with httpd.conf supplied
Product: Red Hat High Availability Server
Classification: Retired
Component: piranha (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Phil Copeland
Wil Harris
Depends On:
  Show dependency treegraph
Reported: 2001-01-03 13:03 EST by Dale Lovelace
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-03 15:34:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Red Hat Bugzilla 2001-01-03 13:03:55 EST
With the httpd.conf that is supplied for the new "standalone"
piranha-gui, there is no line to specify where the "ResourceConfig" or
"AccessConfig" files are, so apache uses the defaults of
/etc/httpd/conf/srm.conf and /etc/httpd/conf/access.conf. If you by chance
have something in either of those files the standalone piranha-gui apache
server tries to use it. For example, a lot of people have their
"DocumentRoot" in srm.conf. This makes piranha-gui use the DocumentRoot
specified in srm.conf instead of the one in httpd.conf. You can alleviate
this problem by putting these two lines in your supplied httpd.conf file.

ResourceConfig /dev/null
AccessConfig /dev/null
Comment 1 Red Hat Bugzilla 2001-01-03 15:34:34 EST
Thanks. I'm obviously going senile in my old age 8)

I've made alreations as appropriate in the VCS I'll see about getting a new cut
down for tonight

Comment 2 Red Hat Bugzilla 2001-05-16 19:31:46 EDT
This is fixed and new RPMs will be posted shortly

Note You need to log in before you can comment on or make changes to this bug.