diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2007-06-02 05:45:14 +0000 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2007-06-02 05:45:14 +0000 |
| commit | 3758f6dad4a3e3fc6f45ee03eca8f5c687653190 (patch) | |
| tree | 51b24da44b472a5ea0820f7476101741f45ab7bb /man4/rtc.4 | |
| parent | 91749c0ca61906788ce16862318132ec770f17e6 (diff) | |
Minor wording fixes
Diffstat (limited to 'man4/rtc.4')
| -rw-r--r-- | man4/rtc.4 | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -62,12 +62,12 @@ The system clock reports seconds and microseconds since a start point, defined to be the POSIX Epoch: Jan 1, 1970, 0:00 UTC. (One common implementation counts timer interrupts, once per "jiffy", at a frequency of 100, 250, or 1000 Hz.) -That is, it's supposed to report wall clock time, which RTCs also do. +That is, it is supposed to report wall clock time, which RTCs also do. A key difference between an RTC and the system clock is that RTCs run even when the system is in a low power state (including "off"), and the system clock can't. -Until it's initialized, the system clock can only report time since +Until it is initialized, the system clock can only report time since system boot ... not since the POSIX Epoch. So at boot time, and after resuming from a system low power state, the system clock will often be set to the current wall clock time using an RTC. |