It doesn't run other than the boot script, and right before reboot,
except if I run it from a prompt.
> hwclock should never run while the system is at the production runlevel.
Agreed.
> Maybe you have some cron running hwclock? With ntpd enabled you shouldn't
I don't think anything is, I looked recently and didn't find anything.
> CMOS at the same time. Anyway the race seems very small to me and I would
> be surprised if you triggered it at shutdown time.
Yes, since it runs fine when the system is up (and it can be interrupted
with ^C :))
> Also make sure your hwclock binary is safe. If a binary hwclock out there
> is buggy then we are wasting time looking at the kernel 8).
I don't think that's it, but it could be:
> andrea@laser:~/kernel > hwclock -v
> hwclock 2.4c/util-linux 2.9t
$ hwclock -v
hwclock 2.4c/util-linux 2.9w
-- Ryan Murray (rmurray@cyberhqz.com, rmurray@glenayre.com) Software Designer, Glenayre Technologies Inc. The opinions expressed here are my own.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/