What's new

time disparity of 947357 minutes detected

lfbb

Regular Contributor
Oct 19 22:17:03 dnsmasq-dhcp[526]: DHCPINFORM(br0) 192.168.2.119 40:61:86:e6:2a:98
Oct 19 22:17:03 dnsmasq-dhcp[526]: DHCPACK(br0) 192.168.2.119 40:61:86:e6:2a:98 HPE310PT
Oct 19 22:17:03 pppd[501]: System time change detected.
Oct 19 22:17:03 dnsmasq-dhcp[526]: DHCPREQUEST(br0) 192.168.2.116 00:23:6c:94:fa:67
Oct 19 22:17:03 dnsmasq-dhcp[526]: DHCPACK(br0) 192.168.2.116 00:23:6c:94:fa:67
Oct 19 22:17:49 crond[529]: time disparity of 947357 minutes detected
Oct 19 22:19:37 dnsmasq-dhcp[526]: DHCPINFORM(br0) 192.168.2.119 40:61:86:e6:2a:98
Oct 19 22:19:37 dnsmasq-dhcp[526]: DHCPACK(br0) 192.168.2.119 40:61:86:e6:2a:98 HPE310PT
Oct 19 22:20:42 dnsmasq-dhcp[526]: DHCPINFORM(br0) 192.168.2.119 40:61:86:e6:2a:98
What does that "time disparity of 947357 minutes detected" mean?

- lfbb
 
It simply means that crond was started before the router's clock could be set through NTP, and it just noticed the huge time difference caused by the clock getting properly set. Just ignore that message.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top