You are not logged in.
Pages: 1
i dont think there was any significant change to the way the timezone or the system clock is being generated during boot.
i know from checking rc.sysinit that the changes proposed the 14/12/2009 in the arch-dev-public mailing list have yet to propagate to an upgrade.
ive checked the pacman log and there is nothing related to rc.sysinit
last upgrade in november:
$ cat /var/log/pacman.log |grep initscripts
[2008-11-17 17:05] installed initscripts (2008.05-1)
[2008-11-17 20:25] upgraded initscripts (2008.05-1 -> 2008.09-2)
[2009-02-13 23:28] upgraded initscripts (2008.09-2 -> 2009.01-1)
[2009-03-08 02:50] upgraded initscripts (2009.01-1 -> 2009.03-1)
[2009-03-10 22:23] upgraded initscripts (2009.03-1 -> 2009.03-2)
[2009-07-18 15:02] upgraded initscripts (2009.03-2 -> 2009.07-2)
[2009-07-20 00:48] upgraded initscripts (2009.07-2 -> 2009.07-3)
[2009-08-24 09:48] upgraded initscripts (2009.07-3 -> 2009.08-1)
[2009-11-07 10:36] upgraded initscripts (2009.08-1 -> 2009.11-1)
the issue seems not to be battery related since the time is off by a day only, or a couple of hours. or...well.. its quite odd.
this is a big issue due to hdd mount times in the future...annoy the hell out of me. ive fixed the issue hackishly using opentp but its run after hdds are mounted.
Offline
Does rm /var/lib/hwclock/adjtime help?
Offline
as tavianator said,
removing /var/lib/hwclock/adjtime
may help
also, you may want to install openntpd (open network time protocol daemon) - its a very simple and fast/lighweight daemon which you can setup by reading the wiki
also, if you are runing another OS (windows/etc)
you should have the following entry in the /etc/rc.conf file
HARDWARECLOCK="localtime" # "localtime" / "UTC"
If people do not believe that mathematics is simple, it is only because they do not realize how complicated life is.
Simplicity is the ultimate sophistication.
Offline
Pages: 1