On Wed, 23 Jun 2010 09:46:32 +0100 Mark Rogers mark@quarella.co.uk allegedly wrote:
One of which is that it does seem quite easy to make a config error in one virtual server that brings down the whole server, and all the unrelated virtual servers with it. Testing the configuration doesn't always work either.
To me, an ideal server would run multiple virtual servers as independently as possible. That means that a fault in one shouldn't be able to bring down the whole server, but it also means that one code running in one site should not be able to access directories from other sites (in much the same way that, for example, PureFTP has a single ftpuser at the filesystem level but prevents one user from accessing another users files).
Of-course the biggest problem is that I have a server with a load of virtual servers on it (sharing an IP), so migrating to a new server means migrating all the sites in one go, although I could run some test sites on a different port initially. So this may all be pie-in-the-sky thinking, but what other web servers are worth a look?
Mark
I use, and can recommend, lighttpd. It is very lightweight (in both memory and cpu resource requirements), the configuration syntax is relatively straightforward, and it handles virtual servers pretty well. But my requirements are modest (low traffic for personal websites on a VPS).
However, your question got me thinking and I have done some checking with my own setup. I deliberately introduced some syntax errors in the configuration of a virtual server and tested with "lighttpd -t -f configfile" (the lighty equivalent of of apache2 -t) and found that I could get an error through the testing ("syntax ok") which would then cause the server to fail to reload.
So the problem is not confined to apache unfortunately.
Mick
---------------------------------------------------------------------
The text file for RFC 854 contains exactly 854 lines. Do you think there is any cosmic significance in this?
Douglas E Comer - Internetworking with TCP/IP Volume 1
http://www.ietf.org/rfc/rfc854.txt ---------------------------------------------------------------------