Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is it necessary to CHROOT the Cherokee Webserver (It runs as a user with no shell and restricted priveleges).

How do I go about finding the requirements of Cherokee (for putting it in a chroot jail) and is it practical to run multiple websites all with their own version of Cherokee and (in some cases) PHP CGI?

share|improve this question
Multiple webservers: Did you mean on one server? With one IP and Domain? That question is not specific enough. – Kissaki Mar 1 '11 at 9:14

You are not strictly required to, it will function without being in a chroot. However, it is considered a best practice. This is because if someone hacks your website, and gets shell access, they only get access to the very few libraries and programs needed to make the webserver run. Without a chroot, they would have gained access to your whole system.

As far as running several copies of cherokee in thier own chroots, I believe this will fail, as each copy will be trying to listen for traffic on port 80, and find that they can't since the first launched copy of cherokee is already listening in.

However, chrooting is a complex process, and I would not recommend doing it if you are not comfortable compiling your own copy of cherokee.

share|improve this answer
Ports to be bound can be changed. The webservers may also be bound to individual IP-adresses on one server or even independent servers. The question is not specific enough here, but this answer is too simplified. – Kissaki Mar 1 '11 at 9:15

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.