Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29019 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79437 invoked by uid 1010); 25 Apr 2007 15:21:46 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 79422 invoked from network); 25 Apr 2007 15:21:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Apr 2007 15:21:46 -0000 Authentication-Results: pb1.pair.com header.from=rquadling@googlemail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=rquadling@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 66.249.92.173 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rquadling@googlemail.com X-Host-Fingerprint: 66.249.92.173 ug-out-1314.google.com Linux 2.4/2.6 Received: from [66.249.92.173] ([66.249.92.173:16641] helo=ug-out-1314.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D7/4A-25889-7027F264 for ; Wed, 25 Apr 2007 11:21:45 -0400 Received: by ug-out-1314.google.com with SMTP id o4so412824uge for ; Wed, 25 Apr 2007 08:21:41 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=trNtRS4RwCqrd4pj+PC73h5FZcf7jjFwDhsrBZHMr4AeClyvaMjtueZYWAM9T2LuI7jxFd7NuuJgno6C/inqSIoVoCw2+EN9KtlyE7D145dLyfN7S3cqyZbeA3LTI2111U6g+l9OMjtBz92NzMVGNyZmSDozGVf2DW6xaHTy+w4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=sqJ7sjhOg91g5d2chVGdAg2tyVuorEb6PSlDbd2lw4VehrhubZBXezccD+hi5AC+hoc5tdHp32Zo73z6sB8rNJFkYE3dCCQmO+ENl8yXqJsaorbzf8ii3iqPf84GVgIShnQKR5SzGmkZgXnz1SBMzNXfleZwH9tJWnvgkiak4o8= Received: by 10.78.122.16 with SMTP id u16mr195611huc.1177514501113; Wed, 25 Apr 2007 08:21:41 -0700 (PDT) Received: by 10.78.75.16 with HTTP; Wed, 25 Apr 2007 08:21:41 -0700 (PDT) Message-ID: <10845a340704250821v28b0b7f6v1b08a7937727c113@mail.gmail.com> Date: Wed, 25 Apr 2007 16:21:41 +0100 Reply-To: RQuadling@GoogleMail.com To: internals MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Killing an ISAPI thread. From: rquadling@googlemail.com ("Richard Quadling") Hi. Running PHP via ISAPI on Sambar Server. I have a script which is allowed to take a long time. The user has an Abort option and via clever use of sessions, the script can be terminated. All fine. Sometimes, the user is too dumb to abort it when it has to do a LOT more work than they expect. In looking at the server threads, I see many of these scripts loaded, all doing their job correctly but without ever being able to send there details anywhere. I understand that I can't just terminate the PHP isapi.dll as that would bugger up the server, but does PHP have a mechanism by which a thread that it is looking after can be terminated by the server making a call to the isapi.dll. I was thinking that if the max_exec_time could be "manipulated" externally for a single thread within the dll, then the engine would suddenly realise it had taken too long and would terminate. Ideas? Regards, Richard Quadling. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"