PHP :: Bug #39322 :: proc_terminate(): loosing process resource

Bug #39322

proc_terminate(): loosing process resource

Submitted:

2006-10-31 16:22 UTC

Modified:

2007-02-14 19:22 UTC

Votes:	2
Avg. Score:	5.0 ± 0.0
Reproduced:	2 of 2 (100.0%)
Same Version:	2 (100.0%)
Same OS:	1 (50.0%)

From:

c dot affolter at stepping-stone dot ch

Assigned:

Status:

Closed

Package:

Program Execution

PHP Version:

OS:

Private report:

CVE-ID:

None

[2006-10-31 16:22 UTC] c dot affolter at stepping-stone dot ch

Description:
------------
After sending a signal via proc_terminate() to a process, the process resource gets closed immediately.
This means that calling proc_get_status() afterwards, will throw a warning about an invalid process resource.

This behaviour is somewhat cumbersomely, since you're unable to check if it was your signal which has caused the process to terminate or if the process has stopped.

Is this a bug or an undocumented behaviour?

BTW:
Sending a signal via the shell or through posix_kill(), will retain the status for the first proc_get_status() call. 

Reproduce code:
---------------
<?php
$descriptors = array(
    0 => array('pipe', 'r'),
    1 => array('pipe', 'w'),
    2 => array('pipe', 'w'));

$pipes = array();

$process = proc_open('/bin/sleep 120', $descriptors, $pipes);

proc_terminate($process);
var_dump(proc_get_status($process));

?>



Expected result:
----------------
array(8) {
  ["command"]=>
  string(14) "/bin/sleep 120"
  ["pid"]=>
  int(23011)
  ["running"]=>
  bool(false)
  ["signaled"]=>
  bool(true)
  ["stopped"]=>
  bool(false)
  ["exitcode"]=>
  int(-1)
  ["termsig"]=>
  int(15)
  ["stopsig"]=>
  int(0)
}

Actual result:
--------------
Warning: proc_get_status(): 7 is not a valid process resource in ...

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2007-01-23 22:18 UTC] viraptor+phpbug at gmail dot com

I'd rather like to see proc_terminate act like documented:

"proc_terminate() allows you terminate the process and continue with other tasks. You may poll the process (to see if it has stopped yet) by using the proc_get_status() function."

If a known workaround is to send posix_kill, which does... exactly what proc_terminate is supposed to do, why not implement proc_terminate as:

stat = proc_get_status(proc);
if(stat['running']) posix_kill(stat['pid'], sig);

?
+ update the $proc options as needed. That would be much more useful.
Additionaly not every signal actually kills process, so resource should not be destroyed after SIGTERM.
Please correct code, not docs.

[2007-01-23 22:26 UTC] nlopess@php.net

I agree proc_terminate() shouldn't destruct the resource (I also come across theis problem myself..)

[2007-02-14 19:22 UTC] nlopess@php.net

This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.

[2011-09-07 18:09 UTC] rasmus@php.net

Automatic comment from SVN on behalf of rasmus
Revision: http://svn.php.net/viewvc/?view=revision&amp;revision=316379
Log: This test was added to verify that bug 39322 was fixed, which the test
does test for and this works. However, it consistently failed because
it relied on a SIGHUP not terminating a sh -c /usr/bin/nohup sleep 50
process which doesn't work because the SIGHUP goes to the sh process
not the nohup'ed sleep process. So, I have sped up the test and removed
the nohup and instead of trying to SIGHUP I am just doing the equivalent
of a kill 0 on it to verify that the resource sticks around.