Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16945 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52043 invoked by uid 1010); 27 Jun 2005 18:58:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 52028 invoked from network); 27 Jun 2005 18:58:12 -0000 Received: from unknown (HELO ohgaki.net) (127.0.0.1) by localhost with SMTP; 27 Jun 2005 18:58:12 -0000 X-Host-Fingerprint: 219.166.150.11 mx1.es-i.jp Linux 2.4 w/o timestamps Received: from ([219.166.150.11:59280] helo=mx1.es-i.jp) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id C9/4A-00424-34C40C24 for ; Mon, 27 Jun 2005 14:58:12 -0400 Received: (qmail 21542 invoked by uid 501); 27 Jun 2005 18:58:07 -0000 Received: from yohgaki@ohgaki.net by mx1.es-i.jp by uid 401 with qmail-scanner-1.20 (clamscan: 0.65. spamassassin: 2.60. Clear:RC:1(192.168.100.202):. Processed in 0.01415 secs); 27 Jun 2005 18:58:07 -0000 X-Qmail-Scanner-Mail-From: yohgaki@ohgaki.net via mx1.es-i.jp X-Qmail-Scanner: 1.20 (Clear:RC:1(192.168.100.202):. Processed in 0.01415 secs) Received: from unknown (HELO ?127.0.0.1?) (192.168.100.202) by mx1.es-i.jp with SMTP; 27 Jun 2005 18:58:06 -0000 Message-ID: <42C04C47.6070808@ohgaki.net> Date: Tue, 28 Jun 2005 03:58:15 +0900 User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: Derick Rethans CC: internals@lists.php.net References: <42BFA1A5.6030607@ohgaki.net> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] sysvsem module: release_sysvsem_sem and lockup(semaphore leak) From: yohgaki@ohgaki.net (Yasuo Ohgaki) Derick Rethans wrote: > On Mon, 27 Jun 2005, Yasuo Ohgaki wrote: > > >>Since release_sysvsem_sem has error message while releasing acquired >>semaphores (both PHP_4_4 and PHP_5_1), it may end up with semaphore >>leak when error handler is used. >> >>The error message is useful for debugging, so the error message >>output should be configurable with ini setting. Although this workaround >>is not perfect solution, but it works in most cases. If there isn't a better >>idea, I'll add new ini directive to the module. > > > We should not add more ini settings, we've enough of them already. > > Derick > I'll just comment out problematic line that may cause server lockup. -- Yasuo Ohgaki