The Monday 2004-11-01 at 00:56 +0100, Örn Hansen wrote:
It's what it *SHOULD* do, but look at here:
citadel:~ # hwclock mån 1 nov 2004 00.53.47 -0.452386 sekunder
citadel:~ # hwclock --utc mån 1 nov 2004 01.54.05 -0.105389 sekunder
hwclock is not ntp. They are diferent things.
I'm in CET, and the correct local time above is 0:53:47 ... alas, NTPD stores the time in LOCAL time, not UTC time, which explains why the clock was thought to be scewed above. Someone made a mess of things, with the implementation of NTPD, or SuSE in the configuration. I definately set my system to be UTC, and not local.
No, you are confusing the meaning of the --utc option. See the man page: --utc --localtime Indicates that the Hardware Clock is kept in Coordinated Universal Time or local time, respectively. It is your choice whether to keep your clock in UTC or local time, but nothing in the clock tells which you've chosen. So this option is how you give that information to hwclock. Those options only tell hwclock how to interpret the hardware - that is, the CMOS - clock. Thus, what the command shows differs. -- Cheers, Carlos Robinson