site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hi Stéphane, Good thought -- I investigated this: - Luke On Jun 19, 2006, at 11:49 AM, Stéphane Sudre wrote: On lundi, juin 19, 2006, at 06:11 PM, Luke Bellandi wrote: Hi Amrit, Because you may not want root to launch the application. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/luke%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Even when running as the root user, the open command launches the app as the regular user. (as in "open /Application/Utilities/Audio\ MIDI\ Setup.app") However, when launching the binary directly as root (as in "/ Applications/Utilities/Audio\ MIDI\ Setup.app/Contents/MacOS/Audio\ MIDI\ Setup"), it will be launched as root. /Applications/Utilities/Activity\ Monitor.app can be used to see which process is owned by which user. How are you launching your application in your postflight script? I would think that using "open /Applications/MyApp.app" should open the application, and return, allowing the postflight script to exit and the Install to complete normally. It could also be interesting to know where the application is supposed to be installed and which authentication you are requiring. This email sent to luke@apple.com This email sent to site_archiver@lists.apple.com