I was able to get this working by switching the caching to the backend
and then just switching it to the front end with clearing the cache
and restarting the services in between. I had done this before and
have even done this from fresh installs to no avail. Well it works
now anyway.
Do I need to upgrade from 1.3 to 2.0, before I can upgrade to 2.2?
Or should I start fresh with version 2.2?
For security reasons I need to update Apache 1.3.41 (Unix) mod_perl to Apache
2.2.22.
Thanks
-
To unsubscribe,
The spec file for httpd-2.4.2 is missing a small addition for the fcgistarter
man page.
[bpm]$ diff -wruN httpd.spec~ httpd.spec
--- httpd.spec~ 2012-04-19 08:51:25.737085249 -0500
+++ httpd.spec 2012-04-19 09:14:35.287676097 -0500
@@ -454,6 +454,7 @@
%{_mandir}/man1/ab.1*
On 19.04.12 13:57, ithier@jdi.socom.mil wrote:
Do I need to upgrade from 1.3 to 2.0, before I can upgrade to 2.2?
No.
Or should I start fresh with version 2.2?
no problems.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail
On Thu, Apr 19, 2012 at 10:16 AM, Brian Millett bmill...@gmail.com wrote:
The spec file for httpd-2.4.2 is missing a small addition for the fcgistarter
man page.
Hi Brian,
It is likely that your post to users@ is sufficient for such a simple
fix (i.e., will reach a developer with
Matthieu Moy matthieu@grenoble-inp.fr writes:
You might also add
AllowOverride None
I'll try that
I did try, and it did not change the problem. Deny directives are still
ignored.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
I did just that today (1.3 2.2). It is simple.
I noted this:
- Delete User/Group/BytesLog directive from vhosts (if you have them).
- BytesLog could be replaced by something like this i think:
LogFormat %{%s}t %B . bytes_count
CustomLog domlogs/example.com-bytes_log bytes_count
- In
On Thu, Apr 19, 2012 at 12:16 PM, Pablo Armando
pablo.arma...@dattatec.com wrote:
I did just that today (1.3 2.2). It is simple.
I noted this:
- Delete User/Group/BytesLog directive from vhosts (if you have them).
- BytesLog could be replaced by something like this i think:
On Tuesday 17 April 2012 14:48:17 Jeroen Geilman wrote:
On 2012-04-17 17:48, John Iliffe wrote:
I am trying to update from 2.2.14 to 2.4.1 and have encountered two
problems. 2.2.14 has been working properly for over 2 years. Pages
are located on a separate directory starting at /www with
After factoring in the suggestions from a number of folks here (thanks!) I
still have problems getting a working configuration.
Many pages depend on PHP and I upgraded PHP to version 5.4.0, compiled it
as an apxs module in conjunction with Apache 2.4.1 resulting in
On Thursday 19 April 2012 14:01:37 John Iliffe wrote:
After factoring in the suggestions from a number of folks here (thanks!)
I still have problems getting a working configuration.
Many pages depend on PHP and I upgraded PHP to version 5.4.0, compiled
it as an apxs module in conjunction
On 4/19/2012 1:01 PM, John Iliffe wrote:
After factoring in the suggestions from a number of folks here (thanks!) I
still have problems getting a working configuration.
Many pages depend on PHP and I upgraded PHP to version 5.4.0, compiled it
as an apxs module
PHP fans everywhere will
As mentioned on this list, 2.4.2 was just released. You will want to
pick up that update.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Thanks. I pick that up tonight.
That puts me back to square one!
One thing I noticed but as it doesn't seem to make any immediate difference
I didn't report it: I installed OpenSSL 1.0.1 and configured Apache as:
--with-openssl=path to openssl-1.0.1
but the start up messages from Apache in
To my knowledge, --with-openssl is not configuration flag. When compiling
2.4.X, the following has worked for me.
--enable-ssl=shared
--with-ssl=/path/to/openssl
For example, I install OpenSSL to /my/application/support and my --with-ssl
argument looks like this:
On Thursday 19 April 2012 15:02:20 James wrote:
To my knowledge, --with-openssl is not configuration flag. When
oops! Yes, mea culpa, a typing error. This upgrade, which is time limited
and crucial, has been such a disaster that now I'm making mistakes where I
should know better.
Thanks for
Greets,
I'm building the httpd 2.4.2 RPM packages for our systems.
Using Centos 6.2 I have built RPM's for APR 1.4 and APR-devel 1.4 those
installed fine. I thought this was going to be easy. :)
All other dependencies have been cleared but the last. distcache-devel.
I'm wondering if
Bit more information regarding this
I am able to configure, make, and install httpd. I guess with apr-devel
out of the way I'll be trying this method for now.
I checked the src rpm for httpd-2.2.14-2 and found this comment in
httpd.spec
* Tue Dec 8 2009 Joe Orton jor...@redhat.com -
18 matches
Mail list logo
