Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Issues with proc_* functions and PHP '--enable-sigchild' configure command option

Open
#58 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
cli

Research direction

Start by reproducing the reported behavior with PHP compiled using --enable-sigchild and the default proc_* path, then compare it with the useExec option. Review the linked PHP bug reports and determine whether phpinfo() exposes enough information to detect the configuration; done means successful commands no longer return an error in that environment.

Written by the indexing model from the issue text.

Description

Hi,

It looks like PHP compiled with '--enable-sigchild' will have issues with php-shellcommand when proc_* functions are used (by default). php-shellcommand will return an error when the command executes successfully.

The reason is discussed in the following PHP bug reports:
https://bugs.php.net/bug.php?id=61873
https://bugs.php.net/bug.php?id=71804

There is no issue when using useExec option on a system with PHP compiled with '--enable-sigchild'.

There is not much that can be done other than detecting the '--enable-sigchild' configure command option and adding the useExec option. Unfortunately, there doesn't appear to be any way to do this aside from parsing phpinfo().

Is there any other way to handle this issue?

Thanks.

Dominant language
PHP
Stars
325
Forks
53
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mikehaertl/php-shellcommand

All issues in mikehaertl/php-shellcommand

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.