[PATCH] Abort powerd when no cpufreq(4) support is found

[Nate Lawson]

On Apr 9, 2012, at 9:51 AM, Robert Millan wrote:

> Hi Nate,
> 
> El 9 d’abril de 2012 18:06, Nate Lawson <nate at root.org> ha escrit:
>> The message is fine, but I think an error code of 0 is wrong. Powerd didn't start, whereas 0 means the daemon launched successfully.
> 
> In that case, may I suggest that we return one of the error codes
> recommended by sysexists(3)?  EX_UNAVAILABLE seems close enough to the
> reason we're aborting.

Fine by me. The rc framework or user should be the one to interpret the error code and realize that it's ok that it's not running (not supported).

-Nate