One gotcha you may run into, some .conf parameters have changed.You can't just copy the old 2.2.x .conf file over to 2.4.x without checking. Since some of the changes occurred in various levels of 2.2 they aren't all referenced in the migration notes.
Been there, done that, got the bruises to prove it! John ============================================================= On 02/08/12 09:45 PM, Tom Browder wrote:
On Thu, Aug 2, 2012 at 5:35 PM, Mauricio Tavares<raubvogel@xxxxxxxxx> wrote:On Thu, Aug 2, 2012 at 5:53 PM, Tom Browder<tom.browder@xxxxxxxxx> wrote:...The "Debian" option should make the situation somewhat easier, BUT, will it overwrite existing configuration files? It's not supposed to, but has anyone tried to do this?...IMHO, if you are building apache from source, you should be able to tell it to use a different location not only for its binaries but also for its config files. At least that is what I have done with, say, openldap before. Do configure -h (I think) and check the options to specify where you want it to install itself. Then you just write a quick startup script for this new apache; if you need I might have something you can use for ideas.Thanks, Marcio--good idea. I'll call for help if I get stuck. Best regards, -Tom --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|