Process of chrooting: mod_chroot vs. ChrootDir in Apache2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I've been using mod_fastcgi with mod_chroot for some time, but recently
learnt that there is ChrootDir in the core of Apache2 by now.

However, when using ChrootDir from Apache2, and disabling mod_chroot, it
appears that the mod_fastcgi processes are not started inside the
chroot, but outside of it.

This might be related to where mod_chroot hooks into the Apache2
processing and where Apache2 itself now does the call to chroot.

Is there some documentation available regarding this?

Are there plans/intentions to fix this, so that mod_fastcgi behaves in
the same way regardless of using either mod_chroot or the core directive?


Thanks,
Daniel

- -- 
http://daniel.hahler.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNERmYfAK/hT/mPgARAvOwAKCSyPMWdtjq87oN1q04VOZ1iA4JUACgmYMA
x4kd3sNsmh2Xi1JjYsZKOy4=
=Hip0
-----END PGP SIGNATURE-----