Ron Johnson wrote:
On 2009-08-17 15:22, Hugo Vanwoerkom wrote:
Hi,
Just did a giant Sid dist-upgrade. It caused trouble with the clock.
The hwclock is kept at local time. And 'hwclock --debug --directisa'
says just that.
But now when the system boots it thinks that the time is UTC time and
so for the local time it subtracts 5 hours.
That causes e2fsck to fail on all partitions in /etc/fstab because the
time in their superblocks is 5 hours ahead of what it thinks the local
time is.
date gives the true local time -5 hours
date -u gives the true local time
/etc/timezone has SystemV/CST6CDT
So my question is: who at boot time is responsible for realizing that
the hwclock is kept in local time and UTC time?
Maybe this would cure your problems:
$ grep -n UTC /etc/default/*
/etc/default/rcS:13:UTC=yes
Sadly enough that says UTC=no on the failing system and on the
non-failing system too.
Unless it's a bug in initscripts.
Hugo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org