Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:2082
Return-Path: <brianm@dealnews.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 2529 invoked from network); 29 May 2003 17:54:15 -0000
Received: from unknown (HELO mail.dealnews.com) (129.41.69.137)
  by pb1.pair.com with SMTP; 29 May 2003 17:54:15 -0000
Received: (qmail 19472 invoked from network); 29 May 2003 17:54:15 -0000
Received: from unknown (HELO doughboy) (65.88.166.133)
  by 10.1.1.7 with SMTP; 29 May 2003 17:54:15 -0000
Message-ID: <01c301c3260b$512bda30$0100a8c0@doughboy>
To: <internals@lists.php.net>
Date: Thu, 29 May 2003 12:54:14 -0500
Organization: dealnews.com, Inc.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: exec in CLI vs. mod_php
From: brianm@dealnews.com ("Brian Moon")

I am trying to figure out what is internally different about exec between
CLI and mod_php.

If exec() a script from CLI and said script forks, I get my prompt right
back.

test.php
------------
<?php

exec("/home/brianm/fork.php");

?>


fork.php
------------
#!/usr/local/bin/php
<?php

$pid = pcntl_fork();

if ($pid == -1) {
    trigger_error("Could not fork __FILE__", E_USER_ERROR);
    exit();
} elseif($pid>0) {
    exit();
}

touch("/tmp/file.txt");
sleep(5);

?>

However, if I run test.php from mod_php in Apache, the parent zombies and
exec() waits for the forked process to finish.

What is the difference here and is there any hope of having exec in mod_php
work the same as it does in CLI?

Brian Moon
dealnews.com