Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19439 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12226 invoked by uid 1010); 6 Oct 2005 10:57:52 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 12211 invoked from network); 6 Oct 2005 10:57:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2005 10:57:52 -0000 X-Host-Fingerprint: 193.109.255.35 mail58.messagelabs.com Linux 2.4/2.6 Received: from ([193.109.255.35:45008] helo=mail58.messagelabs.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id D4/60-54476-D2305434 for ; Thu, 06 Oct 2005 06:57:50 -0400 X-VirusChecked: Checked X-Env-Sender: dj@tangozebra.com X-Msg-Ref: server-7.tower-58.messagelabs.com!1128596250!101808721!1 X-StarScan-Version: 5.4.15; banners=tangozebra.com,-,- X-Originating-IP: [85.133.1.66] Received: (qmail 13573 invoked from network); 6 Oct 2005 10:57:43 -0000 Received: from unknown (HELO hermes.tangozebra.com) (85.133.1.66) by server-7.tower-58.messagelabs.com with SMTP; 6 Oct 2005 10:57:43 -0000 Received: from minerva (unknown [85.133.1.67]) by hermes.tangozebra.com (Postfix on SuSE Linux eMail Server 3.1) with ESMTP id BEE581B42F9; Thu, 6 Oct 2005 10:37:31 +0000 (GMT) Received: from dj by minerva with local (Exim 3.35 #1 (Debian)) id 1ENTRN-0003fq-00; Thu, 06 Oct 2005 11:57:33 +0100 Date: Thu, 6 Oct 2005 11:57:33 +0100 To: internals@lists.php.net Message-ID: <20051006105733.GJ11922@tangozebra.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: james aylett Subject: Re: [PHP-DEV] Re: CLI in PHP6 From: james.aylett@tangozebra.com (James Aylett) On Thu, Oct 06, 2005 at 12:33:16PM +0200, Peter Brodersen wrote: > Jani mentioned in http://bugs.php.net/bug.php?id=34483 : "Running a > PHP for 24 hours (under windows) is REALLY not supported or suggested. > It's definately nothing to do with PHP but your OS." (and "Try this on > a real OS, like Linux") > > Maybe this was what you were thinking of. > > I can't see any reason for that statement, though. For early consumers versions of Windows (95, 98, ME) I wouldn't recommend running a process for that long if you rely on it. For NT-based versions, including consumer editions, there should be no problems in running scripts for as long as you like. This particular bug report was against Windows 2000 Server, which should have no problems. I would heavily dispute the statement that it's definitely the OS and not PHP - there are plenty of processes that run happily for months on W2K Server. James -- james aylett, chief technical architect tangozebra 020 7535 9814 ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________