Age | Commit message (Collapse) | Author | Files |
|
Signed-off-by: Sebastien Luttringer <seblu@seblu.net>
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
|
|
For virtualized machines, the hardware clock doesn't actually exist, so all
hwclock calls fail and print error messages during system startup, shutdown,
and the hourly adjtime cronjob. By explicitly looking for HARDWARECLOCK to
be set to 'UTC' or 'localtime', all other values will result in hwclock
calls being skipped (e.g. set the variable to 'none').
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
The hwclock man page recommends calling hwclock with --adjust
at start time, and periodically during system run. So let's do
that here.
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|