Time to slow down and be more careful

[Hal Murray]

gem at rellim.com said:
> I guess you have not read my comments, and Hal's comments, to the bug where
> we both show, in different ways, why the pivot is just a bug. 

I wouldn't call the pivot a bug, just unnecessary if the system time is 
"close enough".

Without that pivot, things will screwup if the correct time is 2039 and the 
system time is close to 1970.  That will happen in a just booted system 
without RTC if it doesn't have something  else that gets a sane time.

----------

I just rebooted a Raspberry Pi.  Somebody is setting the system time.  I 
don't know who/where.

>From /var/log/messages

Apr 18 01:11:57 rp10 rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" 
x-pid="420" x-info="http://www.rsyslog.com"] exiting on signal 15.
Apr 18 01:12:00 rp10 rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" 
x-pid="376" x-info="http://www.rsyslog.com"] start

>From /var/log/syslog

Apr 18 00:17:01 rp10 CRON[4095]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Apr 18 01:11:57 rp10 systemd[1]: Started Turns off Raspberry Pi display 
backlight on shutdown/reboot.

Apr 18 01:12:01 rp10 ntpd[433]: ntpd play-0.9.7+467 2017-04-15T07:29:36Z: 
Starting
Apr 18 01:12:01 rp10 ntpd[433]: Command line: /usr/local/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:111
Apr 18 01:12:01 rp10 ntp[393]: Starting NTP server: ntpd.
Apr 18 01:12:01 rp10 ntpd[434]: proto: precision = 1.042 usec (-20)
Apr 18 01:12:01 rp10 ntpd[434]: successfully locked into RAM
Apr 18 01:12:01 rp10 ntpd[434]: switching logging to file 
/var/log/ntp/ntpd.log


-- 
These are my opinions.  I hate spam.