Re: Process Termination Detection
Re: Process Termination Detection
- Subject: Re: Process Termination Detection
- From: "Shawn Erickson" <email@hidden>
- Date: Mon, 17 Nov 2008 13:59:35 -0800
On Sat, Nov 15, 2008 at 5:22 AM, Terry Lambert <email@hidden> wrote:
> Maybe you can tell us a little bit more about the program you are trying to
> attack, and why knowing that it has exitted will facilitate your attack, and
> how narrow a time window you believe you have before the attack would fail,
> and we could help you narrow things down.
No attempt to attack anything here...
In a nut shell ... we have a small "cluster" of processes that
together make up our product. Part of this cluster of processes are
launched by a single LaunchDaemon and the other part of this cluster
of processes are launched by one or more LaunchAgents (aqua session or
pre-login). The launch agent cluster up communicates with the launch
daemon, etc. As part of this product we have the concept of processes
that depend on other processes and hence need to know when a member of
this cluster of processes dies (killed, crashed out, etc.) so we can
take action to recover or tear down possibly orphaned processes (and
possibly collect crash information).
We are evaluating built-in methods to do this process watching as well
as looking at methods we can implement using IPC internal to our
process cluster. Basically trying to explore the options available
while we figure out how best to meld that into our product code base
which was originally tooled for Windows.
On a side note we plan for all of our processes (executables) to be
code signed with using same identity since the cluster of processes
together make up on product from the end users point of view.
-Shawn
_______________________________________________
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