Though I have an RTC on both Pi, I install always install chrony On my primary server, I have chrony running using NTS servers as its time source. I allow clients from the LAN on this machine. I have all other machines that can run it use chrony with my LAN server as the only source. If a device only has a time source (NTP) field, I use the LAN address of the main server. Though the load is low, it keeps additional traffic off my WAN and has proven to be accurate over the years. More so that NTPD in my location.
I too have come to look for fake-hwclock and remove it. On Tuesday, August 23, 2022 at 12:06:10 PM UTC-4 cric...@pobox.com wrote: > My solution was to install ntp, plus add a wait routine in > bin/user/extensions that waits for ntpq -pn to > report sync'd time. I use that code on the rest of my Rpi's as well. Can > send if interested. FWIW, the RPi that > runs my weather station does have a RTC stacked on the serial port > (pre-dates said code block). > > On Monday, August 22, 2022 at 5:34:27 PM UTC-6 pa...@pauland.net wrote: > >> fake-hwclock is just plain silly, by design it sets the OS time to a >> known wrong state with the premise that it's a better than nothing choice. >> Funny the further down the rabbit hole I go the more I see that I don't >> like. Such as debian setting NTPD or timesyncd to use >> debian.pool.ntp.org ntp servers. >> I certainly don't trust their list of rotating servers to all be >> accurate. Always set systems to use known highly available servers I trust. >> It's a jungle out there a minimum you need, Belt, Suspenders, and of >> course a good quality Tin Foil Hat. >> >> Paul >> >> >> >> >> >> >> >> >> >> so strange that a simple thing lige starting >> >> On Mon, Aug 22, 2022 at 5:28 PM vince <vince...@gmail.com> wrote: >> >>> On Monday, August 22, 2022 at 10:12:59 AM UTC-7 pa...@pauland.net wrote: >>> >>>> Problem I've seen in the past was that on a Rasberry Pi installrd NTP , >>>> like I have on every system I've installed since 2004, yet after a power >>>> outage weeWx started with a bad Os Time. Investigated and found that if I >>>> removed purged fake-hwclock the expected wait for ntp worked. Now on some >>>> systems I install ntp others I don't, if it's a PI remove fake-hwclock and >>>> even if the machine has a RTC I enable systemd-time-wait-sync. >>>> >>> >>> Yes - but be careful there. Lots of os now have that blasted >>> fake-hwclock kludge. >>> >>> I remove fake-hwclock and install/enable ntpd everywhere and it's nice >>> and simple and reliable. No need to edit anything in weewx at all, which >>> is an added plus. >>> >>> The pi time-related details are in the FAQ >>> <https://github.com/weewx/weewx/wiki/faq-raspi-nuances> and wiki >>> <https://github.com/weewx/weewx/wiki/Time-services>. >>> >>> >>> >>> -- >>> 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 weewx-user+...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/221eacc6-2833-420d-ad00-0d6cb4d56c00n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/221eacc6-2833-420d-ad00-0d6cb4d56c00n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e2ac455b-f4bf-459a-a2e0-67d7e626b2cfn%40googlegroups.com.
