Someone who is a Raspian expert can correct me on this if I'm wrong: I seem to recall that Raspian, if stripped of fake-hwclock, etc., does NOT start up with the universal Linux Jan 1970 date but uses a date that corresponds to the release date of that version of Raspian. This means that programs/scripts that rely on looking for an "old" date (say, pre-2000 or pre-1990) as an indication of a 'bad' time setting won't work properly.
However, I can't remember where I stumbled on this nor does a quick Google search help me. I don't want to spread bad information. Can anyone confirm/refute this? David On Tuesday, 12 March 2019 22:44:26 UTC-4, vince wrote: > > >> On Tue, Mar 12, 2019 at 1:48 PM vince <vince...@gmail.com> wrote: >> >>> >>> Yes - systemd will run its own (not so good) time sync function by >>> default. You really don't have to disable it, if you install ntpd systemd >>> detects that and lets ntpd drive things re: time. >>> >>> >>> > On Tuesday, March 12, 2019 at 3:20:15 PM UTC-7, Thomas Keffer wrote: >> >> But, does it still record the time and try to use that on startup? >> >> > I don't know.... > Certainly no harm in disabling it in systemd to try to make sure, but then > also do the normal disabling of fake-hwclock too I guess. > > Bottom line is we probably want a system with no battery-backed-up clock > to power up cleanly with a time old enough so weewx does its "wait for good > time before starting" thing. That was something like 'wait until the > system clock is newer than the modification date of weewx.conf' or the > like, wasn't it ? > > This stuff'll make you crazy. > > -- 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. For more options, visit https://groups.google.com/d/optout.
