Re: Massive IP address change.

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Rob

I'm not sure how this is a response to what I said.

Nonetheless, there are advantages to multiple server instances. 
Simplicity is one of these. Maybe this can be compared to the simplicity 
in the single modules of modular programming, but some might consider 
that a stretch.

The other is administration - if all of your apps are configured in one 
file, with multiple "listen" directives and virtual hosts or redirects, 
then when you shut it down, you shut down everything. With multiple 
server instances, if there is a problem with one, it does not have to 
affect everyone else.

So there's no right or wrong here - Apache has so many options, so many 
ways to do things - you'd almost think it is Perl! TMTOWTDI - There's 
more than one way to do it!

Vern

On 4/26/2011 6:10 AM, rob@xxxxxxxxx wrote:
> While it may be possible for a good person to get by with one apache
> config file and coding for all the variety of things they may be running
> you often find that "vendor a" wants his own config file and their support
> will look upon a shared config file with about as much disdain as an ERP
> vendor will with a modified order entry program.
>
>
> Rob Berendt
> -- Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 
> Ship to: Dock 108 6928N 400E Kendallville, IN 46755 
> http://www.dekko.com From: Vern Hamberg <vhamberg@xxxxxxxxxxx> To: 
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Date: 
> 04/25/2011 10:07 PM Subject: Re: Massive IP address change. Sent by: 
> midrange-l-bounces@xxxxxxxxxxxx Larry, I think Rob wants to change 
> HTTP stuff - the IP addresses, if any, in the Apache config files. It 
> isn't usually necessary even to have any IP addresses there, but it is 
> certainly an option. There is also the QUSRSYS/QATMHINSTC file - it 
> has a member for each Apache instance - these should NOT be modified, 
> but they do contain the path to the httpd.conf files. HTH Vern