macbook pro slow shutdown 10.8.2

maybe this may also help with problems concerning slow shut down!

https://discussions.apple.com/thread/4515285?tstart=180

That change did it. Tried quite a few other options on the forums. Appreciate the help. 🙂

The happinesss is short lived. The problem WILL return.

Yes...the problem will return. I've posted several times on this long thread and have done all of the fixes. Using Lion on a 2011 MacBook Air, shutdowns typically took two to three seconds. With Mtn. Lion, they were about 30 to 40 seconds. After doing the fix above, my first few shutdowns were almost within 3 seconds. Now, about 40% to 50% of the time I get a three second shutdown. The remainder of the time, the shutdowns take 10 times that long. I really wish Apple would fix this.

BTW...if you haven't submitted a bug report to http://www.apple.com/feedback, then please do so.

Hi,

my Macbook pro 15" Retina shows random slow shutdowns.

Shutdown usually takes less than 2s, but sometimes more than 20s.

Examining the Console logs, I found that com.apple.securityd hangs and was killed after timeout 20s elapsed.

so I did:

sudo defaults write /System/Library/LaunchDaemons/com.apple.securityd ExitTimeOut -int 2

After that com.apple.coreservices.appleid.authentication was hanging 20s

Again:

sudo defaults write /System/Library/LaunchAgents/com.apple.coreservices.appleid.authentication ExitTimeOut -int 2

sudo defaults write /System/Library/LaunchDaemons/com.apple.mDNSResponder ExitTimeOut -int 2

Then com.apple.coreservices.appleevents was the suspect

Furthermore:

sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 2

Then my system is now shutting down faster (<3s).

If I search with the Console

/var/log/com.apple.launchd/launchd-shutdown.system.log

"Exit timeout elapsed" only com.apple.securityd hangs and was killed after timeout 2s elapsed.

My solution of course is temporary. I would appreciate, if this could be FIXED by Apple!

Maybe this helps someone...

If you want this fixed, I'd suggest that you file a bug report as well. Squeaky wheels get greased.

It's insane that a 5400RPM drive on an older Mac can shutdown faster than a new Mac runing 10.8.2.

pjbmil's workaround solves this issue. It's a little scary if you have never edited system files before, but it works.

As I and others have pointed out above, pjbmil's fix works for a short time and/or works some of the time. I still have that fix installed on my two, 2011, MacBook Airs. Before the fix, 100% of the time I got a very slow shutdown--30 to 45 seconds instead of 3 seconds.

After the fix, the first few shutdowns were as fast as they were with Lion. After that, I get a slow shutdown about 50% of the time. That's way better than before, but not a complete fix.

Hi Scott,

the commands I wrote in above post like

sudo defaults write /System/Library/LaunchDaemons/com.apple.securityd ExitTimeOut -int 2

do exactly the same as pjbmil does.

What I found out is, that every few shutdowns there are other services hanging! So it seems, that this helps temporarily, but in deed, it works for those hanging processes, where the patch is applied.

Which processes are hanging you see in Konsole

On the left side you select:

/var/log

then

/com.apple.launchd/

and finally

launchd-shutdown.system.log

On the upper left in the search field type "killing" and you see all processes that have been killed.

here my example:

2006099 com.apple.launchd 1 com.apple.securityd 15 Exit timeout elapsed (2 seconds). Killing

20004607 com.apple.launchd 1 com.apple.launchd.peruser.212 2698 Exit timeout elapsed (20 seconds). Killing

20004643 com.apple.launchd 1 com.apple.launchd.peruser.89 223 Exit timeout elapsed (20 seconds). Killing

As you can see, securityd was killed after 2s (this process was "patched") but the " com.apple.launchd.peruser...." still need 20s to shut down (not patched).

Unfortunately I don't know how to do the same patch with the "peruser" entries...

hey OlliHappyOnMac, and thanks for this method. one thing i noticed is the using the "defaults" command the plist is reformatted as a binary and not a text editor friendly and editable xml file. do you know if there is an argument or option for "default write..." that would keep the plist files in the same format? i managed to open it in xcode, save as a copy as a "Property List XML" and move it back to the appropriate directory but i'd rather not use xcode for this, which won't save changes anyway unless you run it as root.

also note that using the "sudo defaults write ..." method it does change file permissions to -rw------- instead of -rw-r--r-- which is what they should be. not sure if this affects anything but i changed them back just to be sure

sudo chmod og+r (filename)

I cannot believe that Apple hasn't fixed this yet. A 2009 MacBook with a 5400 RPM drive shuts down faster than my 2012 MacBook Pro.

Incredible.

Hi Billy,

you're right: File Permissions are changed etc.

I used the diskutility to repair permissions. This brings everything back to the correct settings.

It also corrects the display format.

Thanks.

I've modded three of my plist files so far and all appears to be well. I wonder though, if these processes are not stopping gracefully and are repeatedly having to be killed, what are the repercussions? does this possibly present other problems in the OS environment down the line?

And so far, how many of the coreservices have we identified as being prone to stalling at shutdown?

so far looks like the main culprits are:

com.apple.securityd

com.apple.coreservices.appleevents

com.apple.coreservices.appleid.authentication

com.apple.mDNSResponder

i personally haven't seen appleid.authentication stall yet but it won't surprise me when it does. i'm gonna go ahead and theorize that launchd is to blame here and not the coreservices themselves. but i guess i'd like really like to know what exactly is causing this, and has Apple officially acknowledged it?

I understand that bugs are inevitable in Software and Operating Systems but it seems to me that for all the billions they make they could have a dept of support personal who moderate these forums and address problems directly.

thanks to everyone for putting heads together and finding a workaround for this. 10.8.2 so far for me has been so-so. lots of little bugs, problems with AFS file sharing speeds, and a horrendous startup time which i'm guessing may again be launchd related. hopefully we see progress with 10.8.3. and soon.