Bug 445596 - mod_suphp ships broken config file
Summary: mod_suphp ships broken config file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mod_suphp
Version: el4
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Andreas Thienemann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: ActualBug
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-07 21:01 UTC by Felix Schwarz
Modified: 2012-03-01 20:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-01 20:02:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Felix Schwarz 2008-05-07 21:01:07 UTC
Description of problem:
mod_suphp installs /etc/suphp.conf which contains unnecessary data in an invalid
syntax.

The config file starts like this:
# This is the Apache server configuration file providing suPHP support..
# It contains the configuration directives to instruct the server how to
# serve php pages while switching to the user context before rendering.
# For directives see <URL:http://httpd.apache.org/docs-2.0/mod/mod_suphp.html>

LoadModule suphp_module modules/mod_suphp.so
...

This is just the mod_suphp.conf which is placed into /etc/httpd/conf.d/, too.

According to upstream the proposed file starts like this
(/doc/suphp.conf-example in upstream tar ball):
[global]
;Path to logfile
logfile=/var/log/suphp.log

;Loglevel
loglevel=info

;User Apache is running as
webserver_user=wwwrun
...


Version-Release number of selected component (if applicable):
0.6.3-1

Comment 1 Felix Schwarz 2008-05-07 21:02:17 UTC
The bad config file will cause errors in the apache error log:
ParsingException in IniFile.cpp:130: Illegal line "# This is the Apache server
configuration file providing suPHP support.."

Comment 2 Kevin Fenzi 2012-03-01 20:02:14 UTC
EPEL-4 has reached end of life and is no longer supported. 

Please retest your bug against EPEL-5 or EPEL-6 and re-open if the bug persists in the packages available in those releases, or file a new bug. 

See: http://lists.fedoraproject.org/pipermail/epel-announce/2012-February/000015.html


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