site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com jeudi 12 mai 2005, à 01:54 AM, Michael Krugman a écrit : My $0.02 _______________________________________________ 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... I am working on a G5 iMac with Tiger 10.4.1 (both updates) installed. We have been using PackageMaker as our installer for our aMac Digital Radiography OS X software. PackageMaker was working perfectly under 10.3 and some of the developer versions of 10.4. [...] One other thing we discovered...if the permissions of the installed file in /Library/StartupItems are not exactly the same as the /Library/StartupItems folder, Tiger will throw an error that says the security settings of a file in /Library/StartupItems must be repaired. It gives the option to fix, decide later or disable. Clicking fix gives a dialog that the repair was complete and you must restart. Clicking the restart button gives the exact same results....icons disappear, finder closes and system hangs until I manually turn the computer off, then on again. If the permissions are correct, the error dialog does not appear, but the system hangs as I explained earlier. Can someone give me a suggestion as to what I can do, if anything, to either stop this problem or work around it? Most of our clients have upgraded to Tiger and it doesn't go over with them very well with respect to manually turning the computer off, then back on again. Help on this is appreciated. 1. It can't be a problem with PackageMaker since PackageMaker does not install Packages, it just builds them. 2. It's probably not a problem with Installer.app because when the permissions are incorrect, you're not seeing the problem from what I understand. BTW "funny" discovery in Tiger, the /Library is now 1775 when it was 775 on previous versions. 3. Are you installing a Kernel Extension in /Library/StartupItems? Because what you're describing looks like a freeze caused by a wrong mutex lock (that's what I was seeing yesterday when testing some mutex locking). Depending on how your startup script is written, your startupitem may get launched on shutdown and your kext may get loaded. This email sent to site_archiver@lists.apple.com