On Wed, 7 Jun 2000, John P. Looney (Kate) wrote:
> <thinks> Yes, it has in the past. It's my PIII desktop in work.
> Pretty much.
> Yeah, but what's that got to do with the price of turnips. The machine
> hasn't been rebooted in (checkes) 21 days. Why should the clock skip
> forward an hour, to resync with the hardware clock ?
cause when the machine suspends the kernel (software) clock stops running.
so upon resume the apm code has to re-init kernel time from somewhere, eg
windows sets RTC (hardware clock) to localtime. However, Linux is probably
expecting your rtc to be in GMT. Hence the hours difference - cause we are
currently in BST, not GMT....
> I'm fairly sure I could fix it, if I could get xntpd to change the
> hardware clock too, but I don't see such an option in the docs...
there's a kernel option called "CONFIG_APM_RTC_IS_GMT". so:
1. If RTC is set to GMT, then enable above kernel option. or 2. If RTC is
in localtime, then make sure above is not enabled.
2. If RTC is in localtime, (cause you need to run windows with correct
time) then disable this option.
Preffered option is 1.
in your case you can probably do:
<check that present time is correct, eg rdate ..>
hwclock --utc --systohc
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!