From the pmset manpage:
STANDBY ARGUMENTS
standby causes kernel energy administration to routinely hibernate a machine after it has slept for a specified time interval. This protects energy whereas asleep. This setting defaults to ON for supported {hardware}. The setting standby will probably be seen in pmset -g if the function is supported on this machine. standbydelayhigh and standbydelaylow specify the delay, in seconds, earlier than writing the hibernation picture to disk and powering off reminiscence for Standby. standbydelayhigh is used when the remaining battery capability is above highstandbythreshold , and standbydelaylow is used when the remaining battery capability is under highstandbythreshold. highstandbythreshold has a default worth of fifty p.c. autopoweroff is enabled by default on supported platforms as an implementation of Lot 6 to the European Vitality-related Merchandise Directive. After sleeping for <autopoweroffdelay> seconds, the system will write a hibernation picture and go right into a decrease energy chipset sleep. Wakeups from this state will take longer than wakeups from common sleep. autopoweroffdelay specifies the delay, in seconds, earlier than getting into autopoweroff mode.
What is the distinction? Each settings, standby and autopoweroff, management when the machine goes into the sleep mode configured with hibernatemode, right?
standbydelaylow and standbydelayhigh accomplish that with respect to the present battery capability, whereas autopoweroffdelay is solely a timer. Why are there these two concurrent methods to do that? How ought to I configure these settings in a manner that is smart?
