Comments on: Apache, For Instance http://www.linux-mag.com/id/4179/ Open Source, Open Standards Sat, 05 Oct 2013 13:48:18 +0000 hourly 1 http://wordpress.org/?v=3.1 By: j2blue http://www.linux-mag.com/id/4179/#comment-4750 j2blue Wed, 30 Nov -0001 00:00:00 +0000 http://www.linux-mag.com/id/4179/#comment-4750 I'm asking on behalf of those who don't know, like me, exactly what the additional consequences of running multiple instances are. For example: should one instance become compromised(hack, bug, ddos) what happens to the other instances? My guess would be that they would happily truck along, though under reduced bandwidth and slices. Is there a way to "pre-direct" a url to the correct port number so the client doesn't have to know the port number in advance? How do multiple instances affect overall system performance, especially under heavy loads? Should chroot techniques be used? I’m asking on behalf of those who don’t know, like me, exactly what the additional consequences of running multiple instances are. For example: should one instance become compromised(hack, bug, ddos) what happens to the other instances? My guess would be that they would happily truck along, though under reduced bandwidth and slices. Is there a way to “pre-direct” a url to the correct port number so the client doesn’t have to know the port number in advance? How do multiple instances affect overall system performance, especially under heavy loads? Should chroot techniques be used?

]]> By: mxyzplk http://www.linux-mag.com/id/4179/#comment-4751 mxyzplk Wed, 30 Nov -0001 00:00:00 +0000 http://www.linux-mag.com/id/4179/#comment-4751 So one answer - nothing about one Apache crashing or being hacked will per se affect another. However, there's a lot of exceptions here since the Apaches are sharing the same OS. If the DoS runs the comp. out of network sockets, or if one Apache's MaxClients setting lets it get run high enough to take up all the box memory, or if an Apache hack allows access to files under another Apache, you have problems.<br /> <br /> chrooting would help with some of these issues - adding VMs, with even more; adding separate servers, with still more; adding distributed data centers, still more... I think the point of the article is that if you really don't care about any of that and just want 2 Apaches running, you can totally do that. So one answer – nothing about one Apache crashing or being hacked will per se affect another. However, there’s a lot of exceptions here since the Apaches are sharing the same OS. If the DoS runs the comp. out of network sockets, or if one Apache’s MaxClients setting lets it get run high enough to take up all the box memory, or if an Apache hack allows access to files under another Apache, you have problems.

chrooting would help with some of these issues – adding VMs, with even more; adding separate servers, with still more; adding distributed data centers, still more… I think the point of the article is that if you really don’t care about any of that and just want 2 Apaches running, you can totally do that.

]]> By: gradyplayer http://www.linux-mag.com/id/4179/#comment-4752 gradyplayer Wed, 30 Nov -0001 00:00:00 +0000 http://www.linux-mag.com/id/4179/#comment-4752 Aside from some exceptions (running 2+ services that only run only on different versions, or with mutually exclusive configurations) almost any configuration can be crammed into one instance of apache with a combination of virtual servers and reverse-proxying. The best use that I can think of would be for testing something like a deployable service that needs to work with php4 and php5, because that type of concurrency is tough to pull off in a single apache instance. Aside from some exceptions (running 2+ services that only run only on different versions, or with mutually exclusive configurations) almost any configuration can be crammed into one instance of apache with a combination of virtual servers and reverse-proxying. The best use that I can think of would be for testing something like a deployable service that needs to work with php4 and php5, because that type of concurrency is tough to pull off in a single apache instance.

]]>