Thanks for the reply -- Our product is a Parental Controls product. The kernel module is responsible for traffic capture that, if it's interesting is then proxied to/from the user space (running as root on *nix, system on Windows, etc.) daemon. The daemon in turn occasionally needs to display UI to users. A user may be in any graphical session on the box (e.g. Windows or OS X Fast User Switching, Screen Sharing, ...). The UI itself is more than just notifications. We allow decisions to be made by the user, prompt to login to our product in some situations, etc.
The "backup plan" on OS X is to use the /Library/LaunchAgents plist system so start agents at user login. This works for most of the cases, but there are times such as in our update process that we need to stop all agents -> update them -> restart them. Hope that helps clarify, Bryan On Thu, Aug 15, 2013 at 6:35 PM, Jerry Krinock <je...@ieee.org> wrote: > Hello, Bryan. Processes launched by agents can spawn other processes, and > these other processes may be GUI processes. Processes may also install and > load additional launch agents. Non-GUI processes (processes without a > connection to the window server) can show rudimentary alerts using the > CFUserNotification API. > > Maybe we need to know a little more about what you're trying to do. > >
_______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/launchd-dev
