I have always maintained that shared hosts should be running
per-security context Apache instances as different users.The problem with that is that it makes name-based virtual
hosts pretty
pointless because each apache instance will at least need an ip
address on its own.It seems you've never heard of suexec, FastCGI, MPM Perchild
(ok, this one is broken) and Zeus (has nothing to do with
Apache, but is a good product). It's possible to have name
based virtual hosts in
Apache2 and PHP processes running in the context of every
user with a patched suexec, mod_fastcgi and one single IP.
I do have - but to me the recommendation above sounded like running a
difference apache instance (i. e. main server process) for every
security context.
-mp.
Hello Matthias,
could you please change to an email client that doesn't scramble
the message id's?
marcus
p.s.: this issue nerves a lot since we loose context. And from time to time
it has to be mentioned it seems :-)
Friday, November 25, 2005, 1:33:12 PM, you wrote:
I have always maintained that shared hosts should be running
per-security context Apache instances as different users.The problem with that is that it makes name-based virtual
hosts pretty
pointless because each apache instance will at least need an ip
address on its own.It seems you've never heard of suexec, FastCGI, MPM Perchild
(ok, this one is broken) and Zeus (has nothing to do with
Apache, but is a good product). It's possible to have name
based virtual hosts in
Apache2 and PHP processes running in the context of every
user with a patched suexec, mod_fastcgi and one single IP.
I do have - but to me the recommendation above sounded like running a
difference apache instance (i. e. main server process) for every
security context.
-mp.
--
Best regards,
Marcus