Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19444 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91434 invoked by uid 1010); 6 Oct 2005 13:49:30 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 91419 invoked from network); 6 Oct 2005 13:49:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2005 13:49:30 -0000 X-Host-Fingerprint: 195.225.34.5 fw01.axit.nl Received: from ([195.225.34.5:18662] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 8C/38-54476-96B25434 for ; Thu, 06 Oct 2005 09:49:29 -0400 Message-ID: <8C.38.54476.96B25434@pb1.pair.com> To: internals@lists.php.net References: <4E0C5C8E5F8C994F90134920DD66E93F011292EE@pearl.hq.booyahnetworks.com> Date: Thu, 6 Oct 2005 15:48:17 +0200 Lines: 68 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Posted-By: 195.225.34.5 Subject: Re: [PHP-DEV] CLI in PHP6 From: r.korving@xit.nl ("Ron Korving") > FWIW A lot :) Thanks for the response. It's good to see it is possible. > However, a process running for a long time (yes, even on > Linux) will also just "die" for no reason. We have a few hints as to > what causes the deaths but don't know what causes the cause. To solve > the problem we created a daemon class that has a lifetime and can make > itself "eternal" if desired. The net effect is a stable daemon(s). Could you get into a little more detail? I don't quite understand what you mean by this daemon class that can make itself "eternal" and how this can turn the situation stable. Thanks, Ron ""J. Allen Dove"" schreef in bericht news:4E0C5C8E5F8C994F90134920DD66E93F011292EE@pearl.hq.booyahnetworks.com... FWIW, we have been running a number of very high-volume PHP CLI daemons for the last 18-20 months with great success. That is not to say it wasn't a challenge to get them as "stable" as a C++ daemon but we have. PHP 4.x CLI seemed to have a mem leak somewhere, PHP 5.x seems to have resolved that. However, a process running for a long time (yes, even on Linux) will also just "die" for no reason. We have a few hints as to what causes the deaths but don't know what causes the cause. To solve the problem we created a daemon class that has a lifetime and can make itself "eternal" if desired. The net effect is a stable daemon(s). We currently process 65-70MM transactions a day with our PHP-based daemons. We chose to try using PHP to share business logic and it paid off. -- Allen -----Original Message----- From: Ron Korving [mailto:r.korving@xit.nl] Sent: Thursday, October 06, 2005 2:49 AM To: internals@lists.php.net Subject: [PHP-DEV] CLI in PHP6 Hi, There was once (can't remember when exactly, so it must be a long time ago) here on PHP CLI scripts in which it came forward that one should not rely on such a script to run forever. And it's true; the scripts sometimes magically and suddenly die. Now I have no clue where this instability (for lack of a better word) comes from, but could it be possible for this to be resolved for PHP6 so that PHP becomes an extremely viable solution for CLI daemon scripts? Thanks, Ron Korving -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php