Thanks for the help. Doing what was asked I figured out and solved the problem. Another administrator added the option nodev to the partition of the chroot. Probably He did not umounted and mounted the partition after that and the service did not stopped, when we restart the machine, the problem appeared.
One question. For security reasons, what the best mount options for the chroot partition? nosuid I already have. Is it advisable to have nodev on the chroot and mount another small /chroot/dev partition (maybe ramdisk), without the nodev option containing the null urandom and random devices? Thanks again. [ ]'s On Thu, Mar 18, 2010 at 7:52 PM, Mike Bird <mgb-deb...@yosemite.net> wrote: > On Wed March 17 2010 19:00:35 Knowledge Seeker wrote: > > That is the problem. > > The permission is set to 666 and the group is root. > > But it still don't work. > > Please post the exact complete error message, and > also the results of the following three commands run > as root as soon as possible after the error occurs: > > # ls -dl /dev > drwxr-xr-x 22 root root 6280 2010-03-14 11:16 /dev > # ls -l /dev/null > crw-rw-rw- 1 root root 1, 3 2010-03-14 11:15 /dev/null > # su www-data -c 'ls -l /dev/null' > crw-rw-rw- 1 root root 1, 3 2010-03-14 11:15 /dev/null > > Is there anything in your Apache config that might > be trying to chroot? > > --Mike Bird > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > http://lists.debian.org/201003181252.37677.mgb-deb...@yosemite.net > > -- Knoseeker
