Following up, another important use case (which turned out to be what caused problems for us in the first case)... At least with some hardware implementations, upon disconnecting and reconnecting the battery, the hardware clock is initialized to a random date/time, which can easily be years in the future. Again, once in this state, the fake-hwclock can never be set back properly under normal usage, and thus overrides the real hwclock on every future boot. -- ............................................................................
*Roddy Shuler* | +1.585.530.7960 | Endless
