Guys Everything you've said so far make complete sense (thanks for that!).
My question now is, did Doug take this into consideration when he build mod_perl v1.27 (w/ PERL_USELARGEFILES=0) and somehow wrote a function that cleans up the data structures from perl? I think I need someone with 'inside information' into mod_perl to comment on this one... Thx again, Jaco Greyling -----Original Message----- From: Ged Haywood [mailto:[EMAIL PROTECTED] Sent: 18 June 2003 14:53 To: Greyling, Jaco Cc: [EMAIL PROTECTED] Subject: RE: non-LFS Apache 1.3.27 w/ LFS Perl 5.8.0 (using mod_perl) Hi Jaco, On Wed, 18 Jun 2003 [EMAIL PROTECTED] wrote: > As you can see it suggests rebuilding mod_perl with > $PERL_USELARGEFILES=0 (which we do) so according to him it will work? Well it's in the list of suggestions, I don't think that's quite the same thing... I guess the bit about nobody listening to the warning is at least as relevant. :) If none of your system is configured to use large file offsets that's fine. It's when you choose to link together different parts, some of which do and some don't that I'd worry. Structure (mis)alignment can cause all kinds of subtle problems, some very obvious and some not, and the more you play with additional modules, interfaces to the Perl guts etc., the more likely you are to come across them before anyone else does. Traditionally the advice is even that you should use the same compiler to build Perl and mod_perl, for exactly this reason. I would always want to make sure that my Perl and mod_perl were both compiled the same way. 73, Ged. Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
