Re: kqueue EVFILT_PROC and child process pid
Re: kqueue EVFILT_PROC and child process pid
- Subject: Re: kqueue EVFILT_PROC and child process pid
- From: Rustam Muginov <email@hidden>
- Date: Mon, 12 Oct 2009 21:50:55 +0400
Thank you for the hint, Terry.
But isnt' it a polling-like behavior?
On Oct 12, 2009, at 1:57 AM, Terry Lambert wrote:
There's popen of ps, which is much preferred to sysctl.
Other than that, we're not going to alert you on new process
creation other than by return code if you are the creator, and at
some point we might even take steps to make it hard for you to do
so, like randomizing pids.
-- Terry
On Oct 11, 2009, at 1:01 PM, Dave Keck <email@hidden> wrote:
You cannot watch for all processes, only processes you created.
After you
fork, you can add a kqueue to watch for the new process' death, in
lieu of
waitpid() or a SIGCHLD signal. You cannot however sit there,
watching for
any random process' death. Mac OS X has no such mechanism, AFAIK.
kevents are perfectly capable of monitoring another, unrelated
process. It's become quite a hobby of mine, actually. :)
As far as getting the the new child's PID, I don't think it's
possible
using the kevent APIs from userland. (sys/event.h mentions "lower
bits
contain the PID of the child", but I think this is kernel-only.)
Of course you could always iterate over the process list checking
each
process' parent PID... there's probably a better way, though.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Sincerely, Rustam Muginov
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden