Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1552 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33380 invoked from network); 16 May 2003 00:53:19 -0000 Received: from unknown (HELO palrel11.hp.com) (156.153.255.246) by pb1.pair.com with SMTP; 16 May 2003 00:53:19 -0000 Received: from xparelay2.ptp.hp.com (xparelay2.ptp.hp.com [15.1.28.65]) by palrel11.hp.com (Postfix) with ESMTP id 3DACE1C0102E for ; Thu, 15 May 2003 17:53:19 -0700 (PDT) Received: from xpabh2.ptp.hp.com (xpabh2.ptp.hp.com [15.1.28.61]) by xparelay2.ptp.hp.com (Postfix) with ESMTP id EBDC61C00A9A for ; Thu, 15 May 2003 17:53:15 -0700 (PDT) Received: by xpabh2.ptp.hp.com with Internet Mail Service (5.5.2655.55) id ; Thu, 15 May 2003 17:53:16 -0700 Message-ID: <123E41AA62E54346A34828E6646156735FDA8C@xsun03.ptp.hp.com> To: internals@lists.php.net Date: Thu, 15 May 2003 17:53:10 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Subject: PHP logging and concurrency From: roshan.naik@hp.com ("NAIK,ROSHAN (HP-Cupertino,ex1)") Looking at the sources I was surprised to see concurrency problems with logging. Multiple processes/threads seem to freely open, write and close the log file without bothering about any synchronization. The function php_log_error() seems to be the function that finally writes to the the log file specified in php.ini. This implementation could lead to a loss of logging information on heavy loads. Would that be correct ? If so, perhaps I (or someone else) could work on fixing it. -- Roshan