OK, I can see that. I really don't have much more information to add. I pulled my hair out for days trying to get the opendir readdir combination to work. While searching, I came across another post that pointed at the specific kernal I am using. I believe it was the way perl behaved with it. This is the kernal image I have currently in my box /boot/vmlinuz-2.4.18-27.7.x I cannot say 100% that I have not rebuilt that box but I think it's still the same. For clarity, I have no experience in kernal programming and was only repeating what I saw in a post and worked for me. Mike
----- Original Message ----- From: "Randal L. Schwartz" <merlyn@stonehenge.com> To: "Mike OK" <[EMAIL PROTECTED]> Cc: "LUKE" <[EMAIL PROTECTED]>; <modperl@perl.apache.org> Sent: January 12, 2006 1:53 PM Subject: Re: -M in modperl > >>>>> "Mike" == Mike OK <[EMAIL PROTECTED]> writes: > > Mike> The problem may lie in the kernal itself. I had a similar problem > Mike> and found that the kernal was to blame. > > This is a broad statement, and generates FUD. Can you be more specific? Can > you say where you thought the Kernel was to blame? Can you show an example? > > This is a bit like blaming the car when you hit the curb while parking. > *Maybe* it's the car, but when millions of people manage to park a car just > fine, it might not be the car. :) > > -- > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 > <merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> > Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. > See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.371 / Virus Database: 267.14.17/227 - Release Date: 2006-01-11 > >
