Well thats very strange because with verbose boot enabled I've only seen it since 10.8.3
my shutdowns are 4-5 secs.. if you don't have ssd don't expect to get miracle from your computer
Weil, my "miracle" was a 45 sec boot and a 3 sec shut down on Snow Leopard, now it's taking "forever" with ML. IF I wanted to wait that long, I'd have stayed with Winblows.
Windows shuts down in seconds.
... Easy fix if you know how but it shouldn't be this way.
Please, how can i do this easy fix? Thanks.
What-a-shame! I think Steve would have already opened up a can of whoopass so this bug would have been fixed long ago.Windows shuts down in seconds.
I seriously doubt that. The higher up in the executive food chain, the less you'll find these people actually putting products through their paces like we do. Especially when it comes to macs. They simply don't have the time and are most likely tethered to iPads and iPhones for the bulk of their corporate lives.What-a-shame! I think Steve would have already opened up a can of whoopass so this bug would have been fixed long ago.
I seriously doubt that. The higher up in the executive food chain, the less you'll find these people actually putting products through their paces like we do. Especially when it comes to macs. They simply don't have the time and are most likely tethered to iPads and iPhones for the bulk of their corporate lives.
Jobs would not hesitate to phone people on weekends if the background color of an icon was slightly off. This bug affects regular shutdowns. It's one of the basic tests when you put an OS through it's paces (reboot time). Such a regression should not make it past QA.I seriously doubt that. The higher up in the executive food chain, the less you'll find these people actually putting products through their paces like we do. Especially when it comes to macs. They simply don't have the time and are most likely tethered to iPads and iPhones for the bulk of their corporate lives.
So no, I can't picture Jobs, Tim Cook or most any other Cupertino exec hunkered over an iMac for very long (if at all) much less using the OSX "Shut Down" command on a networked terminal.
What-a-shame! I think Steve would have already opened up a can of whoopass so this bug would have been fixed long ago.
I seriously doubt that. The higher up in the executive food chain, the less you'll find these people actually putting products through their paces like we do. Especially when it comes to macs. They simply don't have the time and are most likely tethered to iPads and iPhones for the bulk of their corporate lives.
So no, I can't picture Jobs, Tim Cook or most any other Cupertino exec hunkered over an iMac for very long (if at all) much less using the OSX "Shut Down" command on a networked terminal.
Windows shuts down in seconds.
Nobody of any consequence. That and given how long this issue has remained in ML... what do you think?nobody shuts down at Apple?
Please, how can i do this easy fix? Thanks.
In TERMINAL type in below after doing a "Disk Repair Permission" in "Disk Utility" Some may not have done the Disk Repair Permission but it worked for me in doing so and not when I passed on this
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.coreservices.appleevents.plist
sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 2
sudo launchctl load /System/Library/LaunchDaemons/com.apple.coreservices.appleevents.plist
Nobody of any consequence. That and given how long this issue has remained in ML... what do you think?
Thanks SR45 working Good on Imac with Mountain Lion 10.8.3 !!!
1) Repairing permissions
2) The only thing I had to change is : On Terminal doing ----> su Enter password Enter and then Copy and Paste the second line : sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 2 and Enter !!!!
Opening Terminal and doing exactly as U write the Terminal doesnt recognize commands !?!? Doing something Wrong !?!? However now Mountain Lion SHUT DOWN AT SPEED OF LIGHT !!!! Many Thks !!!!!
In TERMINAL type in below after doing a "Disk Repair Permission" in "Disk Utility" Some may not have done the Disk Repair Permission but it worked for me in doing so and not when I passed on this
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.coreservices.appleevents.plist
sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 2
sudo launchctl load /System/Library/LaunchDaemons/com.apple.coreservices.appleevents.plist
I am truly curious ... why does this matter in the slightest?
10.8.4 beta was released, I would be interested in knowing if this problem has been resolved yet.