SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
NOTES<\/a>
FILES<\/a>
HISTORY<\/a>
AUTHORS<\/a>
COPYRIGHT<\/a>
SEE ALSO<\/a>
AVAILABILITY<\/a> <\/p>\n
\n
NAME <\/a> <\/h2>\nrtcwake \u2212 enter a system sleep state until specified wakeup time<\/p>\n
SYNOPSIS <\/a> <\/h2>\nrtcwake<\/b> [options] [\u2212d<\/b> device<\/i>] [\u2212m<\/b> standby_mode<\/i>] {\u2212s<\/b> seconds<\/i>|\u2212t<\/b> time_t<\/i>}<\/p>\nDESCRIPTION <\/a> <\/h2>\nThis program is used to enter a system sleep state and to automatically wake from it at a specified time.<\/p>\n
This uses cross-platform Linux interfaces to enter a system sleep state, and leave it no later than a specified time. It uses any RTC framework driver that supports standard driver model wakeup flags.<\/p>\n
This is normally used like the old apmsleep<\/b> utility, to wake from a suspend state like ACPI S1 (standby) or S3 (suspend-to-RAM). Most platforms can implement those without analogues of BIOS, APM, or ACPI.<\/p>\n
On some systems, this can also be used like nvram-wakeup<\/b>, waking from states like ACPI S4 (suspend to disk). Not all systems have persistent media that are appropriate for such suspend modes.<\/p>\n
Note that alarm functionality depends on hardware; not every RTC is able to setup an alarm up to 24 hours in the future.<\/p>\n
The suspend setup may be interrupted by active hardware; for example wireless USB input devices that continue to send events for some fraction of a second after the return key is pressed. rtcwake<\/b> tries to avoid this problem and it waits to terminal to settle down before entering a system sleep.<\/p>\nOPTIONS <\/a> <\/h2>\n\u2212A<\/b>, \u2212\u2212adjfile<\/b> file<\/i><\/p>\n
Specify an alternative path to the adjust file.<\/p>\n
\u2212a<\/b>, \u2212\u2212auto<\/b><\/p>\n
Read the clock mode (whether the hardware clock is set to UTC or local time) from the adjtime<\/i> file, where hwclock<\/b>(8) stores that information. This is the default.<\/p>\n
\u2212\u2212date<\/b> timestamp<\/i><\/p>\n
Set the wakeup time to the value of the timestamp. Format of the timestamp can be any of the following:<\/p>\n
![\"Image](\"grohtml-1172341.png\")
<\/p>\n
\u2212d<\/b>, \u2212\u2212device<\/b> device<\/i><\/p>\n
Use the specified device<\/i> instead of rtc0<\/b> as realtime clock. This option is only relevant if your system has more than one RTC. You may specify rtc1<\/b>, rtc2<\/b>, … here.<\/p>\n
\u2212l<\/b>, \u2212\u2212local<\/b><\/p>\n
Assume that the hardware clock is set to local time, regardless of the contents of the adjtime<\/i> file.<\/p>\n
\u2212\u2212list\u2212modes<\/b><\/p>\n
List available \u2212\u2212mode option arguments.<\/p>\n
\u2212m<\/b>, \u2212\u2212mode<\/b> mode<\/i><\/p>\n
Go into the given standby state. Valid values for mode<\/i> are:
standby<\/b><\/p>\n
ACPI state S1. This state offers minimal, though real, power savings, while providing a very low-latency transition back to a working system. This is the default mode.<\/p>\n
\n\n<\/td>\n \nfreeze<\/b><\/p>\n<\/td>\n
<\/td>\n \nThe processes are frozen, all the devices are suspended and all the processors idled. This state is a general state that does not need any platform-specific support, but it saves less power than Suspend-to-RAM, because the system is still in a running state. (Available since Linux 3.9.)<\/p>\n<\/td>\n<\/tr>\n
\n<\/td>\n \nmem<\/b><\/p>\n<\/td>\n
<\/td>\n \nACPI state S3 (Suspend-to-RAM). This state offers significant power savings as everything in the system is put into a low-power state, except for memory, which is placed in self-refresh mode to retain its contents.<\/p>\n<\/td>\n<\/tr>\n
\n<\/td>\n \ndisk<\/b><\/p>\n<\/td>\n
<\/td>\n \nACPI state S4 (Suspend-to-disk). This state offers the greatest power savings, and can be used even in the absence of low-level platform support for power management. This state operates similarly to Suspend-to-RAM, but includes a final step of writing memory contents to disk.<\/p>\n<\/td>\n<\/tr>\n
\n<\/td>\n \noff<\/b><\/p>\n<\/td>\n
<\/td>\n \nACPI state S5 (Poweroff). This is done by calling \u2019\/sbin\/shutdown\u2019. Not officially supported by ACPI, but it usually works.<\/p>\n<\/td>\n<\/tr>\n
\n<\/td>\n \nno<\/b><\/p>\n<\/td>\n
<\/td>\n \nDon\u2019t suspend, only set the RTC wakeup time.<\/p>\n<\/td>\n<\/tr>\n
\n<\/td>\n \non<\/b><\/p>\n<\/td>\n
<\/td>\n \nDon\u2019t suspend, but read the RTC device until an alarm time appears. This mode is useful for debugging.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n
disable<\/b><\/p>\n
Disable a previously set alarm.<\/p>\n
\n\n<\/td>\n \nshow<\/b><\/p>\n<\/td>\n
<\/td>\n \nPrint alarm information in format: “alarm: off|on
rtcwake<\/b> [options] [\u2212d<\/b> device<\/i>] [\u2212m<\/b> standby_mode<\/i>] {\u2212s<\/b> seconds<\/i>|\u2212t<\/b> time_t<\/i>}<\/p>\n This program is used to enter a system sleep state and to automatically wake from it at a specified time.<\/p>\n This uses cross-platform Linux interfaces to enter a system sleep state, and leave it no later than a specified time. It uses any RTC framework driver that supports standard driver model wakeup flags.<\/p>\n This is normally used like the old apmsleep<\/b> utility, to wake from a suspend state like ACPI S1 (standby) or S3 (suspend-to-RAM). Most platforms can implement those without analogues of BIOS, APM, or ACPI.<\/p>\n On some systems, this can also be used like nvram-wakeup<\/b>, waking from states like ACPI S4 (suspend to disk). Not all systems have persistent media that are appropriate for such suspend modes.<\/p>\n Note that alarm functionality depends on hardware; not every RTC is able to setup an alarm up to 24 hours in the future.<\/p>\n The suspend setup may be interrupted by active hardware; for example wireless USB input devices that continue to send events for some fraction of a second after the return key is pressed. rtcwake<\/b> tries to avoid this problem and it waits to terminal to settle down before entering a system sleep.<\/p>\n \u2212A<\/b>, \u2212\u2212adjfile<\/b> file<\/i><\/p>\n Specify an alternative path to the adjust file.<\/p>\n \u2212a<\/b>, \u2212\u2212auto<\/b><\/p>\n Read the clock mode (whether the hardware clock is set to UTC or local time) from the adjtime<\/i> file, where hwclock<\/b>(8) stores that information. This is the default.<\/p>\n \u2212\u2212date<\/b> timestamp<\/i><\/p>\n Set the wakeup time to the value of the timestamp. Format of the timestamp can be any of the following:<\/p>\n \u2212d<\/b>, \u2212\u2212device<\/b> device<\/i><\/p>\n Use the specified device<\/i> instead of rtc0<\/b> as realtime clock. This option is only relevant if your system has more than one RTC. You may specify rtc1<\/b>, rtc2<\/b>, … here.<\/p>\n \u2212l<\/b>, \u2212\u2212local<\/b><\/p>\n Assume that the hardware clock is set to local time, regardless of the contents of the adjtime<\/i> file.<\/p>\n \u2212\u2212list\u2212modes<\/b><\/p>\n List available \u2212\u2212mode option arguments.<\/p>\n \u2212m<\/b>, \u2212\u2212mode<\/b> mode<\/i><\/p>\n Go into the given standby state. Valid values for mode<\/i> are: ACPI state S1. This state offers minimal, though real, power savings, while providing a very low-latency transition back to a working system. This is the default mode.<\/p>\n freeze<\/b><\/p>\n<\/td>\n The processes are frozen, all the devices are suspended and all the processors idled. This state is a general state that does not need any platform-specific support, but it saves less power than Suspend-to-RAM, because the system is still in a running state. (Available since Linux 3.9.)<\/p>\n<\/td>\n<\/tr>\n mem<\/b><\/p>\n<\/td>\n ACPI state S3 (Suspend-to-RAM). This state offers significant power savings as everything in the system is put into a low-power state, except for memory, which is placed in self-refresh mode to retain its contents.<\/p>\n<\/td>\n<\/tr>\n disk<\/b><\/p>\n<\/td>\n ACPI state S4 (Suspend-to-disk). This state offers the greatest power savings, and can be used even in the absence of low-level platform support for power management. This state operates similarly to Suspend-to-RAM, but includes a final step of writing memory contents to disk.<\/p>\n<\/td>\n<\/tr>\n off<\/b><\/p>\n<\/td>\n ACPI state S5 (Poweroff). This is done by calling \u2019\/sbin\/shutdown\u2019. Not officially supported by ACPI, but it usually works.<\/p>\n<\/td>\n<\/tr>\n no<\/b><\/p>\n<\/td>\n Don\u2019t suspend, only set the RTC wakeup time.<\/p>\n<\/td>\n<\/tr>\n on<\/b><\/p>\n<\/td>\n Don\u2019t suspend, but read the RTC device until an alarm time appears. This mode is useful for debugging.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n disable<\/b><\/p>\n Disable a previously set alarm.<\/p>\n show<\/b><\/p>\n<\/td>\n Print alarm information in format: “alarm: off|on DESCRIPTION <\/a> <\/h2>\n
OPTIONS <\/a> <\/h2>\n
<\/p>\n
standby<\/b><\/p>\n\n
\n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n \n
\n <\/td>\n \n <\/td>\n \n