Strange entries in system.log - INTERESTING!! :
Oct 5 07:45:29 Computername.local mDNSResponder[87]: Adding registration domain 62353037.members.btmm.icloud.com.
--2 more entries like the last.--
Oct 5 07:45:29 Computername.local awacsd[103]: Starting awacsd connectivity-78 (Jul 26 2012 14:37:46)
Oct 5 07:45:29 Computername.local com.apple.SecurityServer[17]: Succeeded authorizing right 'system.services.systemconfiguration.network' by client '/System/Library/Frameworks/SystemConfiguration.framework/Versions/A/Resources/SCHelper' [107] for authorization created by '/usr/sbin/awacsd' [103] (100003,0)
Oct 5 07:45:29 --- last message repeated 5 times ---
Oct 5 07:45:29 Computername.local awacsd[103]: Configuring lazy AWACS client: 62353037.p01.members.btmm.icloud.com.
--2 more entries like the last.--
So are there resulting DNS entries? nope.
unix% dig +trace 62353037.members.btmm.icloud.com
<no answer>
But ther's a hint - AWACS and awacsd
awacsd is Apple Wide Area Connectivity Service daemon; man 8 awacsd gives:
BSD System Manager's Manual
awacsd is an executable invoked by launchd to facilitate connections between devices using Back to My Mac. Users cannot invoke awacsd from the command line.
...
Ok, so it's all because I was trying out Back to My Mac.
----------
Ok, so here's another odd entry:
Oct 5 07:45:27 localhost kernel[0]: WARNING - ACPI_SMC_CtrlLoop::initCPUCtrlLoop - no sub-config match for MacBookPro4,1 with 8 p-states, using default stepper instead
A bit of googling and it seems to relate to hackintoshes. But I'm using a real MacBookPro4,1. I wonder if this indicates a real problem. I do want power management (ACPI) to work properly!
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kext/Contents/Resources/MacBookPro4_1.plist seems relevant.
----------
Oct 5 07:45:30 Computername.local SystemStarter[116]: "/etc/rc.local" failed security check: group writable
was useful.
Turns out SystemStarter refused to execute /etc/rc.local, I think because of this failed check.
I predict
sudo chmod g-w /etc/rc.local
fixes that.
The permissions weren't really dangerous:
ls -l /etc/rc.local
-rw-rw---- 1 root wheel 2141 Sep 25 17:59 /etc/rc.local
Oct 5 07:45:29 Computername.local mDNSResponder[87]: Adding registration domain 62353037.members.btmm.icloud.com.
--2 more entries like the last.--
Oct 5 07:45:29 Computername.local awacsd[103]: Starting awacsd connectivity-78 (Jul 26 2012 14:37:46)
Oct 5 07:45:29 Computername.local com.apple.SecurityServer[17]: Succeeded authorizing right 'system.services.systemconfiguration.network' by client '/System/Library/Frameworks/SystemConfiguration.framework/Versions/A/Resources/SCHelper' [107] for authorization created by '/usr/sbin/awacsd' [103] (100003,0)
Oct 5 07:45:29 --- last message repeated 5 times ---
Oct 5 07:45:29 Computername.local awacsd[103]: Configuring lazy AWACS client: 62353037.p01.members.btmm.icloud.com.
--2 more entries like the last.--
So are there resulting DNS entries? nope.
unix% dig +trace 62353037.members.btmm.icloud.com
<no answer>
But ther's a hint - AWACS and awacsd
awacsd is Apple Wide Area Connectivity Service daemon; man 8 awacsd gives:
BSD System Manager's Manual
awacsd is an executable invoked by launchd to facilitate connections between devices using Back to My Mac. Users cannot invoke awacsd from the command line.
...
Ok, so it's all because I was trying out Back to My Mac.
----------
Ok, so here's another odd entry:
Oct 5 07:45:27 localhost kernel[0]: WARNING - ACPI_SMC_CtrlLoop::initCPUCtrlLoop - no sub-config match for MacBookPro4,1 with 8 p-states, using default stepper instead
A bit of googling and it seems to relate to hackintoshes. But I'm using a real MacBookPro4,1. I wonder if this indicates a real problem. I do want power management (ACPI) to work properly!
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kext/Contents/Resources/MacBookPro4_1.plist seems relevant.
----------
Oct 5 07:45:30 Computername.local SystemStarter[116]: "/etc/rc.local" failed security check: group writable
was useful.
Turns out SystemStarter refused to execute /etc/rc.local, I think because of this failed check.
I predict
sudo chmod g-w /etc/rc.local
fixes that.
The permissions weren't really dangerous:
ls -l /etc/rc.local
-rw-rw---- 1 root wheel 2141 Sep 25 17:59 /etc/rc.local
