|
Tom Stambaugh
brooklinetom at gmail.com
Tue Sep 23 19:12:18 EDT 2008
That's good news, I'm always nervous when I touch *anything* on the server. If somebody can confirm that this is, in fact, the case, then I'll feel even better. I any case, think I'll wait until I'm sure I can undo any changes I try before I do anything. Thanks for the quick & helpful reply! Thx, Tom > Apache people do not break APIs between minor patch revision nor > change how existing configuration works. As such, you shouldn't even > need to recompile mod_python, provided that same Apache MPM is used > when you upgrade to 2.2.9. You also shouldn't even need to change the > Apache configuration files. > > Graham > > 2008/9/24 Tom Stambaugh <brooklinetom at gmail.com>: >> My current apache 2.2.8/mod_python 3.3.1 configuration is working very >> nicely. Sadly, however, the log rotate mechanism of apache v2.2.8 is broken >> -- after a rotate, the instance continues to log entries into access_log.1 >> instead of (the new) access_log. This apache bug is apparently fixed in >> v2.2.9. >> >> If I can do so without breaking things, I'd like to upgrade the apache >> server to v 2.2.9 -- but it isn't worth doing if it's going to send me into >> configuration hell for three days. >> >> Does anybody know if apache v2.2.9 works with mod_python 3.3.1? The server >> is running an old (fedora core3/core4) linux. >> >> Thx, >> Tom >> >> _______________________________________________ >> Mod_python mailing list >> Mod_python at modpython.org >> http://mailman.modpython.org/mailman/listinfo/mod_python >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20080923/4f7cce33/attachment-0001.html
|