Bug 159241 - create RPM for mod_perl version 2.0.0
Summary: create RPM for mod_perl version 2.0.0
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mod_perl
Version: 3.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Joe Orton
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-31 20:15 UTC by Peter Halliday
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2005-06-01 14:39:16 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Peter Halliday 2005-05-31 20:15:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Description of problem:
I am experiencing some load problem and memory problem that after reviewing with the mod_perl has been solved in the lastest version of mod_perl.  I want to get a request in to have you all provide an RPM for the latest version as soon as possible.  We using mod_perl highly, and are reliant on this.

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

How reproducible:

Steps to Reproduce:
1. Install mod_perl
2. Use features of mod_perl.
3. Watch degredation of load average, memory usage, and caching

Additional info:

Comment 1 Suzanne Hillman 2005-06-01 14:39:16 UTC
In order to file a RHEL feature request, please either contact Red Hat's
Technical Support line at 888-REDHAT-1 or file a web ticket at
http://www.redhat.com/apps/support/.  Bugzilla is not an official support
channel, has no response guarantees, and may not route your request to the
correct area to assist you.  Using the official support channels above will
guarantee that your issue is handled appropriately and routed to the
individual or group which can best assist you with this issue and will also
allow Red Hat to track the issue, ensuring that any applicable feature
addition is included in all releases and is not dropped from a future update
or major release.

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