On Wednesday 07 February 2001 13:22, you wrote:

On Wed, Feb 07, 2001 at 06:03:36PM +0000, Tor Sigurdsson wrote:

...

Hi,

I updated the apache running on a development system to the latest SuSE- provided "apache 1.3.14: security update for mod_rewrite issue".

are gone.

Has anyone had this problem ?

I tried 1.3.14 package, but it's no go: every child forked from httpd just segfaults. I had to fall back to 1.3.12 and now I'm trying to roll out my own 1.3.17 with mod_perl statically linked. With mod_perl as DSO (the one that shipped in 7.0) I got a footprint of 70 Megs per httpd process. I am more and more inclined to think that I have to compile apache myself to make it usable.

Kastus

...

The installed system is: SuSE 7.0 All recommended patches mod_php4 and the mysql modules for apache.

-tosi Kastus, I should have said something earlier about this, but I've been fighting other wars. I too had a problem with both of the recent apache updates. I simply(sic) reverted to the CD version and things now work. I only use it internally, so it doesn't matter much about security. I'm the only user ;-). I use it for the Doc Host feature, and for development. Perhaps the most recent builds are targeted for 7.1 and a complete regression test for 7.0 wasn't done. I hate to build components myself when there are rpm dependencies. I am not proficient enough at undangling these things to make it worth my time.

Steve

My upgrade to 3.14 broke too, although not right away. Broke after I was installing another piece of software and had to use the depmod -ae option. Have not had the time to try and repair it yet, but it seems I may have to uninstall Apache completly. Matt On Friday 09 February 2001 05:05 pm, John wrote:

The upgrade to SuSE 7.0 seriously broke Apache. I've been unable to get it going since and will probably switch to Boa for the short term as I don't need any fancy modules for what I want. Just straight page serving is find for me. Hopefully they'll get Apache's config right in 7.1.

I must say I'm surprised. I would have thought something as important as Apache would be thoroughly test before a new release.

John

-----Original Message----- From: suse-linux-e-return-46400-john=jmtl.com@lists.suse.com [mailto:suse-linux-e-return-46400-john=jmtl.com@lists.suse.com]On Behalf Of Tor Sigurdsson Sent: 07 February 2001 18:04 To: suse-linux-e@suse.com Subject: [SLE] Update of apache kills modules ( SuSE 7.0 )

Hi,

I updated the apache running on a development system to the latest SuSE- provided "apache 1.3.14: security update for mod_rewrite issue".

This killed the following modules:

#LoadModule layout_module /usr/lib/apache/mod_layout.so #LoadModule cgisock_module /usr/lib/apache/mod_cgisock.so #LoadModule ticket_module /usr/lib/apache/mod_ticket.so #LoadModule random_module /usr/lib/apache/mod_random.so #LoadModule mysql_auth_module /usr/lib/apache/mod_auth_mysql.so #LoadModule dynvhost_module /usr/lib/apache/mod_dynvhost.so #LoadModule gzip_module /usr/lib/apache/mod_gzip.so #LoadModule throttle_module /usr/lib/apache/mod_throttle.so

To get the server up and running I had to comment out these modules in httpd.conf. Apparently apache is left half-crippled when they are gone.

Has anyone had this problem ?

The installed system is: SuSE 7.0 All recommended patches mod_php4 and the mysql modules for apache.

-tosi

-- ______ /---------------------------------------\ \

| Þór Sigurðsson | Tor Sigurdsson | t | | Netmaður | Network Specialist | o | |-----------------------------------------| s | | tosi@rhi.hi.is | i |

\---------------------------------------/_____/

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq