> > As I read it in CVS, chroot() will work even in safe-mode. Isn't this a
bad
> > idea(tm), or am I wrong?
> > If users can chroot in safe-mode, Apache won't serve any more pages
after
> > all children have been chrooted to an empty dir?
>
> uhm, where have you read that? [ curious ]
I just reasoned what could happen. if you chroot a child, I couldn't see a
reason why it'd get respawned (since it doesn't die), but it will become a
useless child, I guessed.
> nope, cause it will run as apache user, and you have to be root to
chroot().
I believe there are webservers which are run as root, or not? If that is the
case, chroot should be disabled in safe-mode IMHO, or better, disabled in
webserver envirment.
Currently the docs say that it is not *wise* to use it in webserver-env, not
that is impossible. That's why I questioned safe-mode restrictions here.
> -- teodor
Jeroen
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
