Anbody using Apache 2.0.5x ?

[nyjimbo]

We would like to move from Apache 1.37 to 2.0.5x because some of our users can tell we are running the older stuff and want to know why. Yeah, we dont really need to go to 2.0 but they think it should be done so if its not painful to upgrade we would like to do it within the next month.

Our servers run Freebsd 6.2, Cpanel 11 and all the latest stuff. Everything is intact and running easyapache is flawless so the machines are pretty solid. We want to keep php at 4.x and mysql at 4.x for now but would like to do the apache thing if possible. We already run 2.0 on our non-cpanel boxes so we know how to trouble shoot it manually, but we dont want to break the easyapache install and do it manually so our boxes maintain full cpanel/upcp/easyapache compatibilty.

What do we need to prepare to go to 2.0 ?. We REALLY need to keep frontpage as well as ALL of our modules we have in 1.37.

Thanks for any info, advice or guidance.

[AtlantisService]

Stage 2

We're having the same problem. We've been using php5 for a few years now (2yrs) on all our servers and everything else is completely updated except for Apache with Cpanel. My advice would be to wait for Stage 2, as there are still some bugs in their support.

Apache 2.2.4 is what we're looking forward too.

[cpanelkenneth]

We would like to move from Apache 1.37 to 2.0.5x because some of our users can tell we are running the older stuff and want to know why. Yeah, we dont really need to go to 2.0 but they think it should be done so if its not painful to upgrade we would like to do it within the next month.

Our servers run Freebsd 6.2, Cpanel 11 and all the latest stuff. Everything is intact and running easyapache is flawless so the machines are pretty solid. We want to keep php at 4.x and mysql at 4.x for now but would like to do the apache thing if possible. We already run 2.0 on our non-cpanel boxes so we know how to trouble shoot it manually, but we dont want to break the easyapache install and do it manually so our boxes maintain full cpanel/upcp/easyapache compatibilty.

What do we need to prepare to go to 2.0 ?. We REALLY need to keep frontpage as well as ALL of our modules we have in 1.37.

Thanks for any info, advice or guidance.

The one that will be a killer is your need for FrontPage. We did some massive work to get FrontPage to support Apache 2.x, since the support was barely there. Other than that, as long as you use --prefix=/usr you should be fine. Well, that and making sure you get the correct modules. Oh, and make certain your httpd.conf is compatible with Apache 2.0, some of the directives changed.


EDIT:
Yeah, i just made the Ea3 delay seem nonsensicle. There is more to it than the above, far more. but for a simple, one machine answer, the above will work.