I'm trying to install apache 2.2.x from a tarball.
And it works. But I'm also trying to install modsecure, and I can't get that to work.
It might help to know what CentOS uses to install Apache when doing the ./configure. === Al
On Mon, Jul 27, 2009 at 5:09 PM, Al Sparksdata345@yahoo.com wrote:
I'm trying to install apache 2.2.x from a tarball.
And it works. But I'm also trying to install modsecure, and I can't get that to work.
It might help to know what CentOS uses to install Apache when doing the ./configure.
There are a couple approaches that may work:
1) Browse to http://your.server.name/server-info
If you haven't disabled it, it will show the server configuration.
2) Grab the sources and check it directly:
yumdownloader --source httpd rpm -ivh http-xxxx.src.rpm
cd /YOURRPMBUILDDIR/SPECS
look at the httpd.spec file in the configure section
Option 1 doesn't work on a new CentOS install of the web server.
I did have to use http://localhost to get the standard CentOS web page up. I went through the /var/www/html directory, and there was nothing there. So I don't know where they put them.
Adding the "server-info" to the URL gives me 404.
Option 2 gives me:
Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirrors.bluehost.com * updates: mirror.unl.edu * addons: mirror.unl.edu * extras: www.cyberuse.com No source RPM found for httpd-2.2.3-22.el5.centos.x86_64 No source RPM found for httpd-2.2.3-22.el5.centos.1.x86_64 No source RPM found for httpd-2.2.3-22.el5.centos.2.x86_64 Nothing to download
=== Al
----- Original Message ---- From: Kwan Lowe kwan.lowe@gmail.com To: CentOS mailing list centos@centos.org Sent: Monday, July 27, 2009 1:26:07 PM Subject: Re: [CentOS] What's the configure specs for the generic Apache install of CentOS x86_64 5.3?
On Mon, Jul 27, 2009 at 5:09 PM, Al Sparksdata345@yahoo.com wrote:
I'm trying to install apache 2.2.x from a tarball.
And it works. But I'm also trying to install modsecure, and I can't get that to work.
It might help to know what CentOS uses to install Apache when doing the ./configure.
There are a couple approaches that may work:
1) Browse to http://your.server.name/server-info
If you haven't disabled it, it will show the server configuration.
2) Grab the sources and check it directly:
yumdownloader --source httpd rpm -ivh http-xxxx.src.rpm
cd /YOURRPMBUILDDIR/SPECS
look at the httpd.spec file in the configure section _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Al Sparks wrote:
Option 1 doesn't work on a new CentOS install of the web server.
I did have to use http://localhost to get the standard CentOS web page up.
I believe that page is served up as an 'ErrorDocument' rather than a documentroot.
You can download the SRPM from one of the mirrors, I usually just browse to the mirror directly instead of using yum out of habbit
http://mirrors.kernel.org/centos/5/updates/SRPMS/httpd-2.2.3-22.el5.centos.2...
What are you looking for in the configure specifically?
nate
Hi,
On Mon, Jul 27, 2009 at 17:09, Al Sparksdata345@yahoo.com wrote:
I'm trying to install apache 2.2.x from a tarball.
Why would you want to do that? CentOS 5.3 already ships Apache 2.2 packaged as an RPM.
But I'm also trying to install modsecure, and I can't get that to work.
I think you mean ModSecurity (http://www.modsecurity.org/), right?
If that's the case, the latest version mod_security-2.5.9 is available from EPEL.
HTH, Filipe
On Mon, Jul 27, 2009 at 5:09 PM, Al Sparksdata345@yahoo.com wrote:
I'm trying to install apache 2.2.x from a tarball.
And it works. But I'm also trying to install modsecure, and I can't get that to work.
It might help to know what CentOS uses to install Apache when doing the ./configure.
Oh.. and another option: /usr/sbin/httpd -V
That will show the compiled options.. :)
Perhaps I can use that to determine what ./configure options to use when compiling, but really, I don't see any differences in the two except some directory paths, and APR version (the CentOS version uses APR 1.3.0 and my version uses APR 1.2.7).
I actually did look into specifying --with-apr=PATH prefix for installed APR or the full path to apr-config --with-apr-util=PATH prefix for installed APU or the full path to
I'll give it a try. === Al
----- Original Message ---- From: Kwan Lowe kwan.lowe@gmail.com To: CentOS mailing list centos@centos.org Sent: Monday, July 27, 2009 1:28:45 PM Subject: Re: [CentOS] What's the configure specs for the generic Apache install of CentOS x86_64 5.3?
On Mon, Jul 27, 2009 at 5:09 PM, Al Sparksdata345@yahoo.com wrote:
I'm trying to install apache 2.2.x from a tarball.
And it works. But I'm also trying to install modsecure, and I can't get that to work.
It might help to know what CentOS uses to install Apache when doing the ./configure.
Oh.. and another option: /usr/sbin/httpd -V
That will show the compiled options.. :) _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Al Sparks wrote:
Perhaps I can use that to determine what ./configure options to use when compiling, but really, I don't see any differences in the two except some directory paths, and APR version (the CentOS version uses APR 1.3.0 and my version uses APR 1.2.7).
I actually did look into specifying --with-apr=PATH prefix for installed APR or the full path to apr-config --with-apr-util=PATH prefix for installed APU or the full path to
I'll give it a try.
It's been a little while since I compiled any apache modules but last time I tried it on CentOS, provided the devel packages were installed it worked without any issues..
nate
On Mon, 2009-07-27 at 16:06 -0700, Al Sparks wrote:
Perhaps I can use that to determine what ./configure options to use when compiling, but really, I don't see any differences in the two except some directory paths, and APR version (the CentOS version uses APR 1.3.0 and my version uses APR 1.2.7).
I actually did look into specifying --with-apr=PATH prefix for installed APR or the full path to apr-config --with-apr-util=PATH prefix for installed APU or the full path to
I'll give it a try. === Al
If you compile your own apache, you lose *ALL* of the patches that upstream has put in place, and you break the rpm-listed definition of what the apache package is. Doesn't sound like a big deal now, right? Wait until later... you'll definitely regret it... EPEL or apxs would be the way to go for this...
-I
At Mon, 27 Jul 2009 16:11:36 -0700 CentOS mailing list centos@centos.org wrote:
On Mon, 2009-07-27 at 16:06 -0700, Al Sparks wrote:
Perhaps I can use that to determine what ./configure options to use when compiling, but really, I don't see any differences in the two except some directory paths, and APR version (the CentOS version uses APR 1.3.0 and my version uses APR 1.2.7).
I actually did look into specifying --with-apr=PATH prefix for installed APR or the full path to apr-config --with-apr-util=PATH prefix for installed APU or the full path to
I'll give it a try. === Al
If you compile your own apache, you lose *ALL* of the patches that upstream has put in place, and you break the rpm-listed definition of what the apache package is. Doesn't sound like a big deal now, right? Wait until later... you'll definitely regret it... EPEL or apxs would be the way to go for this...
Right. The other option, if there is some specific thing you need changed is to grab the source RPM and tweek the .spec file and include your own patch(es). Keep the patch(es), along with a patch file for the .spec file someplace, so you can patch future versions. But Ian is right: you need a really good reason NOT to just use the distro provided RPM, along with whatever extras from EPEL (or rpmforge, etc.) you might need. Also: check out CentOSPlus as well, if you need more bleeding edge or whatever.
-I
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Am 28.07.2009 um 03:23 schrieb Robert Heller:
Right. The other option, if there is some specific thing you need changed is to grab the source RPM and tweek the .spec file and include your own patch(es). Keep the patch(es), along with a patch file for the .spec file someplace, so you can patch future versions. But Ian is right: you need a really good reason NOT to just use the distro provided RPM, along with whatever extras from EPEL (or rpmforge, etc.) you might need. Also: check out CentOSPlus as well, if you need more bleeding edge or whatever.
Ever tried moving the install-location to /usr/local by changing the spec-file?
Last time I looked, there was so much hard-coded stuff in the spec- file that it was almost impossible to change.
Rainer
On Jul 27, 2009, at 6:28 PM, Rainer Duffner rainer@ultra-secure.de wrote:
Am 28.07.2009 um 03:23 schrieb Robert Heller:
Right. The other option, if there is some specific thing you need changed is to grab the source RPM and tweek the .spec file and include your own patch(es). Keep the patch(es), along with a patch file for the .spec file someplace, so you can patch future versions. But Ian is right: you need a really good reason NOT to just use the distro provided RPM, along with whatever extras from EPEL (or rpmforge, etc.) you might need. Also: check out CentOSPlus as well, if you need more bleeding edge or whatever.
Ever tried moving the install-location to /usr/local by changing the spec-file?
Last time I looked, there was so much hard-coded stuff in the spec- file that it was almost impossible to change.
Right - that's kind of the point. If you want to customize your Apache build, then the spec file modification route is the way to go, though you should really know what you're doing and why. If all you want to do is build a non-CentOS/upstream-supplied Apache module, then building an rpm for it is the best way. Failing that, you can use Apache's built-in tool for DSO building: apxs, which is part of the httpd-devel package. Of course, if you want to build everything from source, this may not be the optimum distro for you and you may wish to explore Gentoo...;)
-I
On Mon, 2009-07-27 at 14:09 -0700, Al Sparks wrote:
I'm trying to install apache 2.2.x from a tarball.
That'll pretty much break the apache rpm installation...
And it works. But I'm also trying to install modsecure, and I can't get that to work.
If you stick with the rpm-based Apache installation, it might be as simple as:
yum install httpd-devel apxs -cia mod_security.c
as listed on: http://www.modsecurity.org/documentation/modsecurity-apache/1.9.3/modsecurit...
Of course, you could also grab the RPMS from EPEL... http://download.fedora.redhat.com/pub/epel/5/x86_64/mod_security-2.5.9-1.el5...
It might help to know what CentOS uses to install Apache when doing the ./configure.
That'll be in the SPEC file from the source rpm... also, I believe that be default, you don't get the server-info page unless you're coming in from localhost.
-I
-
Al Sparks -
Filipe Brandenburger -
Ian Forde -
Kwan Lowe -
nate -
Rainer Duffner -
Robert Heller