<note type="warning>You should always test any new version in your
+ environment before putting it into production. For example, you
+ can install the new version with a different
+ <code><em>PREFIX</em></code> and start it on a different port (by
+ adjusting the <directive module="mpm_common">Listen</directive>
+ directive) to test for any incompatibilities before doing the
+ final upgrade.</note>
maybe add to this sentence that these Apaches could then even
run in parallel on the same machine without conflicting with
each other. (Which might not be true in case the configuration
spends ressources that aren't available twice at a time on this
machine, like RAM or file handles - but in principle ...)
Without this parallel usage model the editing of the port numbers
would not make sense, because I could then start both versions
alternately on port 80, switching forward and back between the
Apaches. I wouldn't even need the include structure I described
in my previous posting (I could just make $SERVER_ROOT/conf a
symbolic link to some "common" configuration directory ... and
"make install" would still not overwrite this one, right?).
Regards, Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
