a hint from here: http://apple.stackexchange.com/questions/16306/why-is-the-screen-saver-not-kicking-in solved the issue.
Summary:
from the terminal run 'pmset -g', the output looks like:
$ pmset -g
Active Profiles:
AC Power -1*
Currently in use:
autorestart 0
powerbutton 1
halfdim 1
panicrestart 157680000
hibernatefile /var/vm/sleepimage
networkoversleep 0
disksleep 10
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 15 (imposed by 2319)
womp 0
Active Profiles:
AC Power -1*
Currently in use:
autorestart 0
powerbutton 1
halfdim 1
panicrestart 157680000
hibernatefile /var/vm/sleepimage
networkoversleep 0
disksleep 10
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 15 (imposed by 2319)
womp 0
The process '2319' on the displaysleep line is the problem.
A quick 'ps' and we can find out what the process is:
$ ps -fea | grep 2319
root 2319 1 0 Sep 02 ? 0:04 /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/Ma
root 2319 1 0 Sep 02 ? 0:04 /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/Ma
hmm, no idea what the process is but what the heck, kill it with:
$ sudo kill -9 2319
And the problem is solved.
What I think happened is that I had an aborted remote desktop from my macbook and it left this process 'stuck'. There was very little cpu usage and everything is working find now.
No comments:
Post a Comment