Hi,

I'm trying to jail my Apache server but chroot always gives me an error message when I execute the following command as root.

># chroot /jail /export/srv/www/apache2/bin/httpd
chroot: cannot run command `/export/srv/www/apache2/bin/httpd': No such file or directory

/export/srv/www/apache2/bin/httpd does exist under /jail which is off the filesystem root. Running an strace on the command shows that chroot does successfully change /jail to "/" but the it says that the command path cannot be found.

I don't understand what is wrong. I am running Suse 9.1 Professional.

Thanks for the help!

Just a couple of thoughts:

In your problem description is a typo: after the /jail there is an extra space -- did you intend this or should it be deleted?
Did you ensure, that under /jail (or /export, depends on your first answer ) there are the same directories you need, e. g. /jail/bin etc.? If you intend to handle this another way you could of course change the path after doing chroot?

The command is

># chroot <space> /jail <space> /export/srv/www/apache2/bin/httpd

All directories needed for the jail to run are there includig all dynamic dependancies.

aznluvsmc


I think you need to delete that second space; I have no idea why it should be in there, and I have used chroot several times.

IIRC, *then* you need the rest of the line again to run your app/svc.

HTH,

So from what you're saying the command should be:

chroot /jail/export/srv/www/apache2/bin/httpd /export/srv/www/apache2/bin/httpd


From what I understand the chroot command take the first argument (/jail) and sets that as the new root (/). The command (/export/srv/www/apache2/bin/httpd) is now executed starting at root which in this case is really /jail.

Hi,

Please ignore this post. The problem has been resolved. The command is correct but my symlinks were pointing to a path that doesn't exist once the directory gets chroot'd. Here's a tip, always use relative path links within a chroot jail.