Re: suEXEC witch mod_userdir
Seth Mattinen wrote:
> There are plenty of reasons for ensuring, for example, something doesn't
> walk all over MySQL
Please define "something" and it's consequences.
> or a mail flood doesn't eat up all the resources
For that, you can use a firewall to rate-limit all incoming connections
to all services. Example:
> and take the website down.
That should never happen if your server is well setup.
> Especially if user shell account are permitted on
> the web server.
There is no reason to provide non-chrooted shell accounts. In fact I
don't provide shell accounts at all if I don't know the user, because
you could do too much with them like flood, cpu usage, etc.