Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 66201 invoked from network); 25 Jan 2010 19:45:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jan 2010 19:45:52 -0000 Received: (qmail 76263 invoked by uid 500); 25 Jan 2010 19:45:50 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 76233 invoked by uid 500); 25 Jan 2010 19:45:50 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 76225 invoked by uid 99); 25 Jan 2010 19:45:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 19:45:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pharkins@gmail.com designates 74.125.92.147 as permitted sender) Received: from [74.125.92.147] (HELO qw-out-1920.google.com) (74.125.92.147) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 19:45:40 +0000 Received: by qw-out-1920.google.com with SMTP id 14so3376qwa.40 for ; Mon, 25 Jan 2010 11:45:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=X+NB7RcVNjdKuu6kHk8jXDHuIlS6u2ZZLwrOmORoTog=; b=xJclHXOsZdQHg4wY6Mets5uErTzmZYhudykenBxUOISWhQX9KYb2+ZDSkeTBBfChTu 78ZZYoTPnESVQrA5vMvhU+Ky+HklarQSaMlIL9wFmziYo2KB77wA9kLaa0/VX0Ejl5a8 LgBr02vKuhO0GT4nznu83Ml7///HoyCnR8FgI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lDAUpe/o8KGF6l6ZTjhKY4PGa3Gsl3zfoCoXJ8wqW9szdmueUImcBV+MduJd3JVdxM FDZln2YvJ7uJy116PR9QAPdmWR4Qdr5x5I01l5vGpyu5JYnNVk2OC7s015qixaTHA49C wjdBgEmYUbt55opKa+LoaVJcqBuKnWql0T4x8= MIME-Version: 1.0 Received: by 10.229.131.102 with SMTP id w38mr4086984qcs.35.1264448719139; Mon, 25 Jan 2010 11:45:19 -0800 (PST) In-Reply-To: <4B5DF3F9.7000606@1200group.com> References: <4B5DC1C2.7030009@1200group.com> <714D0BDB-570D-4861-80EA-B8058B8B7137@animalhead.com> <4B5DED03.3040400@1200group.com> <4B5DF3F9.7000606@1200group.com> Date: Mon, 25 Jan 2010 14:45:19 -0500 Message-ID: <66887a3d1001251145p8cfd735i2d06b6ba7b333a91@mail.gmail.com> Subject: Re: mod_perl2 + fork + DBI = Chaos From: Perrin Harkins To: Tosh Cooey Cc: mackenna@animalhead.com, "modperl@perl.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Jan 25, 2010 at 2:41 PM, Tosh Cooey wrote: > Just to follow up on this before anyone spends any time caring about it, the > seg faults could also be because one of the zombie apache2 processes I've > spawned like a Gremlin is answering the request and well... I don't think so. That's not how apache works. > So, if I've done the fork properly and pretend I have apache PIDs 1..10 > running, and the child is 11 and it does it's thing and hits CORE::exit(0) > should that process then die? Yes. Here's some advice about using DBI with forking: http://www.perlmonks.org/?node_id=752289 - Perrin