On Wednesday, March 13, 2019 at 7:29:21 AM UTC-7, David Beach wrote: > 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? > > It's pretty easy to do experimentally. Find a sacrificial pi with just an os there. Yank the power. Power it up. Check its date.
The weewx check is in engine.py at around line 845. It waits until the system time is later than the creation time of the weewx.conf file. So it probably doesn't really matter what time any runtime system comes up with before some ntp(ish) or realtime clock things gets the os an accurate date and 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.
