On 5 February 2015 at 17:08, Chris Walker alug_cdw@the-walker-household.co.uk wrote:
I can't offer a solution but if you think back to a Raspberry Pi, they're not guaranteed to be online or to have a valid clock time so I imagine they save the clock value from when they were last online and use that the next time they fire up. So at least the clock would be near the local time.
If nothing else, it might help you find a solution that works for you.
That would be a good workaround, provided it only fires when the date isn't set by the RTC.
To be honest I find the whole time configuration thing to be pretty messy - lots of different tools, lots of different ways to achieve the same thing, to the point that I don't understand any of them properly!
From my point of view, because this box logs data, what I really want
is that if the clock isn't set then it picks a known time that it hasn't already used (eg 1/1/1970 00:00, but next time it picks 2/1/1970, etc) because otherwise any data it logs gets overwritten in the database because of duplicate timestamps. In which case I think I have some coding to play with :-)