site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Le 18 juin 05, à 19:42, Mike Smith a écrit : On Jun 17, 2005, at 4:35 PM, matt jaffa wrote: Well basically I am trying to associate outgoing traffic with the process that is sending it using a socket filter. It works great, and right now I have my kext sending the pid to a super user process in user space that gets the process path and sends it back. This is less than ideal, I would rather have the kext be able to get this info. I assume you want the path because you use the path to the application to associate the application with some rules regarding the traffic it can send. This isn't very robust though; what if someone moves the application? _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... I would be much more inclined to use the proc_name KPI; in most cases this will remain unique. It's still not such a great idea to depend on the application name, but this is at least resistant to the application moving. Isn't proc_name just the p_comm parameter? In this case, it's not the name of the application, it's sometimes the name of the application, sometimes a shortcut name. My current fear with the stack solution is that it may not survive the switch to the bunnies' processor. This email sent to site_archiver@lists.apple.com