PS. (I just did a BIOS update on one of our old SuperMicros)
To make it more fun there's the level of ACPI support in your kernel,
with whatever fixes and patches you distro vendor backported to it and
whatever compile-time options they chose to not enable -- e.g. RedHat is
notorious for shipping
On 1/30/2014 9:57 AM, Levie, Jim wrote:
> What were you using? I've used etherwake on a variety of 12-14 year old boxes
> successfully.
Sun Fire v20 and x4100 didn't report their power state correctly and
wouldn't reliably wake up. I'm not sure about our old SuperMicros -- but
since I couldn't
On Jan 30, 2014, at 9:42 AM, Dimitri Maziuk wrote:
> On 1/30/2014 7:16 AM, Josh Fisher wrote:
>
>> Perhaps the
>> pm_utils source sheds some light on how a daemon could prevent a
>> system-wide suspend.
>
> Last time I tried I couldn't even get our older machines to WOL. I
> suspect whatever solu
Kern:
I no very little about programming, but here’s the documentation for creating
and releasing a power assertion on OS X. There is a call “IOPMAssertionCreate”
which is available in 10.5, then deprecated in 10.6. Seems it was replaced
with “IOPMAssertionCreateWithDescription” which came in
On 1/30/2014 7:16 AM, Josh Fisher wrote:
> Perhaps the
> pm_utils source sheds some light on how a daemon could prevent a
> system-wide suspend.
Last time I tried I couldn't even get our older machines to WOL. I
suspect whatever solutions there are would only work on some (perhaps
many) recent
On 1/29/2014 1:24 PM, Dimitri Maziuk wrote:
> On 01/29/2014 10:26 AM, Josh Fisher wrote:
>
>> ... The question
>> is, how do you inform Linux and OSX that a daemon is to be considered
>> active even if it would otherwise fall into the category of inactive
>> because, say, there is an open TCP socke
