I don't know if this has already been suggested, but check this file:

/Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist

to see if you have wake up events scheduled.

-- 
Bruce Carter, Center for Creative Computing
University of Notre Dame, Notre Dame, IN  46556


On 5/3/12 12:36 PM, "Dinse, Gregg (NIH/NIEHS) [E]" <[email protected]>
wrote:

>Hello again,
>
>My sleeping monitor (at home) is still waking up throughout the day and
>night, but I do have a new piece of information.  I was sitting at my
>desk 2 mornings ago, the monitor was asleep, and suddenly it woke up.  I
>looked at the Console logs and found the following message:
>
>5/1/12 8:21:40 AM authexec[6281] executing /usr/bin/pmset
>
>I then searched for "pmset" and found many other instances of this
>message and they coincided with times that my wife wrote down, whenever
>she was in the room and noticed my monitor wake up.
>
>I googled "pmset" and found that it is used to adjust power management
>settings.  The error message does not look very informative, at least not
>to me.  It appears that my Mac Pro (running Snow Leopard) keeps executing
>a pmset command, which apparently wakes up my monitor, but I do not know
>how to stop or change this command to prevent my monitor from waking up.
>
>Should a pmset command normally be executed many times per day?
>
>How do I find out what it is doing?
>
>If it is not doing anything useful, how do I stop it or modify it?
>
>Thanks,
>
>Gregg
>
>On 20 Apr 2012, at 8:51 AM, Dinse, Gregg (NIH/NIEHS) [E] wrote:
>
>Hi,
>
>For the last few weeks, the monitor (30" Apple) connected to my Mac Pro
>keeps waking up on its own.  This happens multiple times per day, but it
>does not seem to be on a regular schedule (i.e., not every hour).  I do
>not know what made it start doing this and I do not know how to stop it.
>
>I don't remember making any changes that would be obvious (to me)
>culprits.  I think I might have checked the box in Energy Saving
>preferences to "wake on network activity" so I unchecked that box and
>rebooted, but this did not solve the problem.
>
>Any suggestions?
>
>Thanks,
>
>Gregg
>
>_______________________________________________
>MacOSX-talk mailing list
>[email protected]
>http://www.omnigroup.com/mailman/listinfo/macosx-talk

_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk

Reply via email to