On Tue, 2002-07-02 at 18:17, Dale Scott wrote: > First off, understand I'm a total newbie. I saw a posting the other day > where someone mentioned that they were running Apache 1.3.23. One of the > responders commented on how insecure that was and that the original poster > should upgrade to a newer release. This bothered me as I'm running Apache > 1.3.22.
That's fine. If you've applied Red Hat's errata, you'll still be running that version, but with a different release number... Red Hat's errata did not update to the latest version, it simply fixed the problem in the version originally released with the platform. This avoided a number of cascading dependencies which would otherwise have had to be rebuilt and issued, as well. > Where can I find a newer version of Apache in RPM format for RH 7.2? > > A couple of days later I received an errata notice from RH indicating that > they had a security patch for Apache. I loaded it yesterday afternoon and That's the answer to your question. If you have the errata, you're in good condition. > everything seemed fine but during the early morning hours my httpd server > tried to restart and it barfed when it came to any entry in the config file > that referenced modules/mod_log_config.so. You didn't restart the http server. Logrotate told the running server (the old one) to reload, and it could not reload its modules. Restarting the server fixes the problem. > That file appears to be > corrupted. No it's not. :) > I commented out all references to that file in the httpd config > and restarted the server. Don't do that. Put them back, and restart the server. It'll be fine. > > Last question - what the heck is SIGHUP and why does it keep occuring? SIGHUP is a signal often used to tell daemons to reload themselves. Logrotate's script will send a HUP signal to apache so that it will start using the newly created log files. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
