Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: softfail (nike.apache.org: transitioning domain of
 clint@traveljury.com does not designate 74.125.82.177 as permitted sender)
Subject: Re: Re: I think AuthCookie(DBI) is causing segfaults?
From: Clinton Gormley <clint@traveljury.com>
To: Tosh Cooey <tosh@1200group.com>
Cc: "modperl@perl.apache.org" <modperl@perl.apache.org>
In-Reply-To: <4CDE8F6B.8080000@1200group.com>
References: <4CDC1C22.50108@1200group.com>  <4CDE8F6B.8080000@1200group.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 13 Nov 2010 14:31:28 +0100
Message-ID: <1289655088.8657.3.camel@balrog.traveljury.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Sat, 2010-11-13 at 14:15 +0100, Tosh Cooey wrote:
> I'm not quite ready to declare victory, but I think installing DBD from 
> source and getting more recent versions of DBD was the problem, and it 
> seems there's a lot of little things going wrong with DBD.
> 
> What's going on there?  When did DBD::mysql become so problematic?  It 
> used to run so flawless, even back in the day when you would have to 
> choose between mysql and msql during the install...

Are you using the same version of Perl and gcc that all the rest of your
stack are using?

I compile the whole stack from source, and have none of the problems
that you have described.

(The only gotcha with DBD is don't use a dbh in the parent process,
during startup, then try to reuse it in the child processes. That will
cause a segfault)

clint