> The key to successful chroot'ing, I've found, is running strace or trace
> (depending on your platform) and looking at what files your httpd is
> looking for, importing them into the chroot environment and doing that
> iteratively until you're httpd is running and answering requests fully w/o
> errors. It's a PITA the first time but simple enough to later turn into a
> tarball and/or a shell script for later re-use.
Doesn't sound like a working solution at all for Perl modules :(
You cannot exhaustively test all of your code fast, you will miss
something. So copying /lib/perl5 sounds like a more feasible solution when
you don't have loads of time on your hands.
Of course if you are talking about other libraries and conf files than
directly Perl-related onces, you have a good advise here :)
at least you should run:
strace -e trace=open ...
to skip hunderds of irrelevant traced syscalls...
Thanks, Ian!
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://logilune.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
