On Thu, Feb 17, 2005 at 09:18:31AM -0500, William McKee wrote: > On Thu, Feb 17, 2005 at 10:39:46AM +0000, Joe Orton wrote: > > That was all the non-blocking-vs-blocking stuff. First I'd ask whether > > or not this fails in a non-chroot environment. A chroot will screw up > > all kinds of stuff (e.g. the resolver libraries) unless you set it up > > properly. > > Any pointers to how my host should properly configure the chroot would > be appreciated. Considering that only 17 of 2106 tests failed, it must > be pretty good. I've been running Apache 1.3.x under a jail for a couple > years now without any problems (though I couldn't tell you if the tests > passed; I doubt that they were being run by the Apachetoolbox utility > that I was using to build my server). Is building and running Apache > within a chroot environment going to be a problem under Apache2?
The configure script in 2.0 (actually, the APR library) does several "dynamic" system check; the test in question which could make these mod_perl tests needs to bind to a port on 127.0.0.1 and connect to it. It sounds like you may have issues with that in your jail. Check for the result of the: "checking if O_NONBLOCK setting is inherited from listening sockets" test when you run the configure script. It should be "yes" on FreeBSD. If it's "no", then please preserve capture the srclib/apr/config.log file and upload it somewhere so we can check it. Then try: export ac_cv_o_nonblock_inherited=yes or equivalent in your shell then re-run configure and re-build everything and re-run the mod_perl test suites. > > I presume that httpd+mod_perl were at least configured and built > > *outside* the chroot? > > No, it was built inside the jail. I have no access outside of my jail. I think this is a bit optimistic. I would use a proper FreeBSD 5.3 machine somewhere else to build the software, then deploy prebuilt binaries on the production machine inside the jail. joe
