In Yosemite, there is a log file here:
/private/var/log/coreduetd.log
...but it's always empty. How do I make the system write events to it, assuming there are any?
-
I'm willing to start a bounty on this question, if it looks promising that it can be answered.– RedarmCommented May 23, 2015 at 12:56
Add a comment
|
1 Answer
Unless you know that you've tinkered with the permissions on the file, it should be:
-rw-r--r-- 1 root wheel 0 Oct 18 11:02 /private/var/log/coreduetd.log
This logfile is empty on the 5 Yosemite Macs I have access to.
answered Dec 16, 2014 at 17:57
-
That's my experience as well and looking at CoreDuet's database, I see mentioned: power, thermal, sleep/wake events, etc.. I've also run all sorts of tests (e.g. memory_pressure) and would at some point expect content, if writing was enabled. There also is a private framework, which seems to be for debug logging (/System/Library/PrivateFrameworks/CoreDuetDebugLogging.framework) and I would hope there is a way to enable logging in a way to find content in this log.– RedarmCommented Dec 16, 2014 at 19:42