http://marc.theaimsgroup.com/?t=105042055700005&r=1&w=2
Can someone with .acl filesystem verify that the following proposed solution resolves the problem? (but first reproducing it, so you know that it really solves it) Thanks.
Stas Bekman wrote:
Something definitely has to be done to make this work, since acls are increasingly being supported in the major distributions, including in redhat Very Soon Now.
I certainly agree with you. However won't it be better if perl has changed its -x implementation to perform these access() calls underneath? It'll probably be a much more user-friendlier solution.
I run this through p5p and the answer was:
use filetest 'access';
as it's supposed to make -x take acls into consideration on systems that support the access call.
Can you please test whether this works for you?
Index: lib/Apache/PerlRun.pm =================================================================== RCS file: /home/cvs/modperl/lib/Apache/PerlRun.pm,v retrieving revision 1.41 diff -u -r1.41 PerlRun.pm --- lib/Apache/PerlRun.pm 8 Mar 2003 04:11:09 -0000 1.41 +++ lib/Apache/PerlRun.pm 29 Apr 2003 05:06:24 -0000 @@ -5,6 +5,13 @@ use Apache::Constants qw(:common &OPT_EXECCGI);
BEGIN {
+ if ($] >= 5.006) {
+ require filetest;
+ filetest->import('access');
+ }
+}
+
+BEGIN {
OPT_EXECCGI() if $ENV{MOD_PERL}; #preload, :common are alread pre-loaded
}
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
