Package: acpi-support Version: 0.90-4 Setting the clock (with openntp's "ntpd -s" or with "date 09200837", for example) updates the system clock, but does not commit the changes to the hardware clock. Normally, I'd expect the changes to be committed at shutdown, when "/etc/init.d/hwclock.sh stop" is called.
Acpi does not save the hardware clock at suspend, losing any updates. This is confusing to users that manually set the clock, and should interfere with programs (such as ntp) that measure and attempt to compensate for clock drift over time. Steps to reproduce (as root): # date 09200837 Thu Sep 20 08:37:00 PDT 2007 # <suspend the machine, resume the machine> # date <The update to the clock has been lost> # The file /etc/acpi/resume.d/50-time.sh restores the clock at resume. Adding an analogous file /etc/acpid/suspend.d/50-time.sh should fix the problem. It could run hwclock --systohc. While looking at this problem, I noticed that /etc/rc2.d/Snn-hwclock.sh doesn't exist on this machine. Does debian intentionally avoid setting the hardware clock, or does some other mechanism set the hardware clock on shutdown? If debian intentionally avoids setting the clock by default, perhaps acpid could check to see if debian is configured to save the hardware clock (by checking for /etc/rcN.d/S??-hwclock.sh for the current runlevel, or perhaps by looking in a configuration file). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
