On 23/06/10 09:10, Mark Rogers wrote:
Frustratingly, "apache2 -t" does not report any config errors but this problem crashes the server.
This has got me thinking....
Apache may be the world leader, but then Windows is the leading O/S on much the same basis, and Apache does have its flaws.
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?