> On Oct 23, 2014, at 11:50 AM, H J <[email protected]> wrote: > > 2) Steps taken so far > -- Followed tutorial at <http://stuartcheshire.org/SleepProxy/index.html>. > But the tutorial contemplates using an always-on Mac as the SleepProxy > provider, so I can't see how to do any of part one ("Setting up the Sleep > Proxy Mac"). > -- Verified (via both "avahi-browse -tva" from the Ubuntu box and "dns-sd -B > _sleep-proxy._udp local" from one of the target Macs, when they are awake) > that the SleepProxy is running on the ATV. However, dns-sd shows its Instance > Name as "70-35-60-63.1 My Apple TV", which I think means its priority = 70. > I'm not sure how to change it to priority = 10, as per the tutorial, nor > whether or not this matters.
It doesn't matter. You can't change the priority of AppleTVs or Airports. Setting a Mac as a server and setting the priority to 10 just makes sure that that Mac will be used as the sleep proxy rather than any other devices you may have on the network. > -- Verified that "Wake for network access" is checked in System Prefs>Energy > Saver (according to <support.apple.com/kb/ht3774>, this means the machine > supports both wired and wireless WOL). > -- Verified that remote login is enabled in System Prefs>Sharing, and that I > can connect via ssh when the Mac is awake. > -- Applied the "-UseInternalSleepProxy 0" tweak to > com.apple.mDNSResponder.plist (as described in Part Two of the tutorial). Did you run `sudo killall -INFO mDNSResponder` and check the output? You can launch Console.app and type in mDNSResponder in the search field to filter what's shown. As the website above says, you should see a filled in (black) sun next to services that can be proxied - if you see an open sun, that means no sleep proxy server was found. > -- Set both PrioritizeNetworkReachabilityOverSleep and DarkWake (as described > at http://mactips.dwhoard.com/mactips/system/wake-on-demand). I wouldn't change those. You should set them back to the defaults. > 3) Where this fails > -- When the target machine is left alone overnight, it goes into "full" sleep > (presumably display _and_ hard drive). When this happens, it disappears from > the network altogether (i.e. not visible to avahi-browse) and does not wake > in response to etherwake, wakeonlan, or ssh connection attempts. It remains > this way until someone physically wakes up the machine (via keypress or > mouse), after which everything works as expected. > It sounds like it's not registering with the sleep proxy server at all, though I'm not sure of that. Can you wake it up from sleep right after it's gone to sleep? In Console.app, type in 'RTC' (without the quotes). You should see some lines like this: Oct 24 02:59:18 kernel[0]: Wake reason: RTC (Alarm) Oct 24 02:59:18 kernel[0]: RTC: Maintenance 2014/10/24 08:47:15, sleep 2014/10/24 06:59:18 Oct 24 04:48:17 kernel[0]: Wake reason: RTC (Alarm) Oct 24 04:48:17 kernel[0]: RTC: Maintenance 2014/10/24 10:36:15, sleep 2014/10/24 08:48:17 The important thing to see is the RTC: Maintenance line, and you should see it happen roughly every 2 hours that the computer is asleep. Note that the time won't be right - the clock hasn't been updated at the point that these are logged, so it will actually be the time the machine last went to sleep rather than the time it has woken up. It should still be roughly every 2 hours, though. The reason this is important is that the sleep proxy server will only proxy a record for 2 hours, and if the computer doesn't refresh its status somewhere in that time, the sleep proxy server will just drop it and you won't be able to wake the computer up after that. Sometimes, too, the sleep proxy server itself can get in a bad state. You may want to try rebooting your AppleTV and see if that clears things up. ------------------------------------------------------- Michael Nickerson _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
