Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93946
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain mudsite.com designates 209.85.223.196 as permitted sender)
MIME-Version: 1.0
Date: Mon, 13 Jun 2016 18:18:31 +0000
Message-ID: <CADVQu1QvzLe3kst_pQEA6MOBKUzKazmHFUy0dwbYb9q52EG9XQ@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=94eb2c05a27c0912c005352cebd9
Subject: pcntl_signal & sa_siginfo
From: dave@mudsite.com (David Walker)

--94eb2c05a27c0912c005352cebd9
Content-Type: text/plain; charset=UTF-8

Hi All,

Long-time lurker, first time questioner here.  I'm currently working on a
project wherein I end up forking off many subprocesses, but am trying to
keep tabs on the progress of individual forks by having the children send a
signal back up to their parent every so often.

pcntl_socket, allows me to listen for expected user signals from processes,
however, the handler only allows a single argument the signalnumber.  I
would like to extend the handler to accept a possible second argument.  If
compiled on a system with __siginfo_t it would use SA_SIGINFO when setting
up the signal listener, and populate a second argument to the user-callback
which could be an array with at leas sa_pid and sa_uid (contents of _kill).

So I'd like to source the list to see if this would be something that would
be welcomed, or if there would be other ideas on how to get some more info
of the signal back to the PHP-side of the pcntl_signal.

--
Dave

--94eb2c05a27c0912c005352cebd9--