site_archiver@lists.apple.com Delivered-To: Darwin-dev@lists.apple.com Thank you for explanation, Damien. How fast the kqueue events are delivered to the subscribed process? As fast as the implementation allows. So again, no guarantees.
From kqueue(2)...
-- Damien Sorresso BSD Engineering Apple Inc. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... On Oct 12, 2009, at 10:48 AM, Rustam Muginov wrote: Is it possible that the watched process would spawn child process, kill it, and then spawn another one before the watching application get notified? Sure. The kernel will deliver events to you as fast as it can, but it doesn't make any guarantees regarding latency. Also keep in mind that the kernel could deliver the event to you with near-zero latency, but you're still responsible for dequeuing it on your end. And the thread responsible for that in your code is at the mercy of the kernel's scheduler. Can the regular-user application watch other users/root processes, or it must run on behalf of root? If a process can normally see another process, it can attach an event to it. This email sent to site_archiver@lists.apple.com