vince <[email protected]> writes: > Is there something wrong with the checks in current weewx ? It waits for > the clock to be newer than the last modified date+time of weewx.conf, which > seems to be a reasonable way to be current enough (by some definition). > All you need to do is ensure that the fake-hwclock kludge is not present on > the system and of course install and enable ntpd (so systemd doesn't break > things).
I am not running Linux. On NetBSD, by default, in the absence of a hardware clock, the system clock is initialized to the last sync time of the root filesystem. I gather that this is similar behavior to what fake-hwclock does. But, I thought that in general waiting until the clock was known to be right was good strategy. (Also, I don't understand why bad times are a problem, because it seems that archive records from the hardware have hardware timestamps. But, with a 1.5h power outage, I experienced what I think was recording those records at the wrong time.) -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
