Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 10826 - Bad Apache configuration after run linuxconf
Bad Apache configuration after run linuxconf
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
: 11589 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2000-04-14 15:40 EDT by awhansen
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-24 08:31:49 EDT
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 awhansen 2000-04-14 15:40:14 EDT
When I change with linuxconf the server name from the Apache configuration,
apache not runs anymore, because the server name it puts is incorrect.
And linuxconf puts in the httpd.conf file a line like "PerlHandler ..."
that apache reports as an configuration error.
Comment 1 Anonymous 2000-04-24 08:31:59 EDT
I found that several <Directory> entries get fouled up as well, with an extra
double quotes appearing.

Also, the default <Files> entry included makes it impossible to get the
default "welcome" page (http://yourhostname/) even from the same machine.  This
is easy to fix, but could dissuade a Linux Newbie, and is probably a bit
Comment 2 Nalin Dahyabhai 2000-09-12 14:58:05 EDT
Linuxconf has been known to destroy known-good Apache configurations.  We're
disabling the module until it can be debugged.
Comment 3 Nalin Dahyabhai 2000-09-12 15:13:52 EDT
*** Bug 11589 has been marked as a duplicate of this bug. ***

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