druck  wrote:
> On 23/01/2019 14:28, Chris Green wrote:
> > Yes, absolutely, but when it was working OK (i.e. upto 06:49) it would
> > have the correct time, so that's probably the correct time.  I quite
> > agree that when booting the time is basically random until it gets a
> > LAN connection up and can ask someone the time.
>
> It's not random, it has a fake hardware clock module which periodically
> saves the current time, then uses it on a reboot before ntp kicks in.
>
> e.g. Times in Syslog may look something like
>
> 2115 Save Clock
> 2118 Crash
> 2115 Restarting
> 2120 Got NTP
>
I didn't mean random in the sense of like a random number, I just
meant not the actual time.

I believe *some* systems do what you're describing but I don't think
it's by any means universal in all distributions.  In particular I
know that Beaglebone systems don't reboot to 'nearly the right time'
by default.  I was thinking that Pi works the same but maybe not.

--
Chris Green
·

--- SoupGate-Win32 v1.05