On 04/06/15 08:34, Christos Zoulas wrote:
In article <55228206.5080703%hiwaay.net@localhost>, William A. Mahaffey III <wam%hiwaay.net@localhost> wrote:On 04/05/15 19:21, William A. Mahaffey III wrote:On 04/05/15 17:59, Christos Zoulas wrote:In article <5521A935.4050809%hiwaay.net@localhost>, William A. Mahaffey III <wam%hiwaay.net@localhost> wrote:I absolutely agree, I wish I had figured this out a while back :-). It does bring up another possible issue for me. My LAN is not always connected to the internet, I disconnect at night & whenever I know I will be away from the computer for some time (mow the lawn, run errands, eat, etc.), thus I am only connected a few hours per day. How will ntpd handle this intermittent connection (to internet time servers) circumstance ? TIA & thanks again.It depends; when you get disconnected, the clock will drift. Depending on the system (how well it keeps time) and how long you stay disconnected will dictate the approach. If you drift for < 600 seconds, you can use ntpd -x (i.e. keep running ntpd with -x and it will correct the drift when it is reconnected); if you drift more (and I hope you don't), you should create a script or a cron job to restart ntpdate and ntpd. christosExcellent, thanks for the pointers :-). I just kicked it off w/ flags of '-ggggx', to also let it slew the time if necessary upon reconnection, we'll see how it goes. If this works as it should, it is far superior to what I was doing in the past, so thanks again.Alright, still a minor issue. I kicked off ntpd w/ my ISP as the only server & flags of '-ggggx', to let it slew time if necessary. It wrote out a ntp.drift file a few min. later, w/ 0.000 in it, & has never updated it. The time is also off by several min. as of this A.M. I have the following in my messages file: Apr 3 22:00:01 rpi syslogd[555]: restart Apr 3 22:04:50 rpi ntpd[3084]: ntpd 4.2.8-o Fri Dec 19 21:49:44 EST 2014 (import): Starting Apr 3 22:04:50 rpi ntpd[3084]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pidI don't see -g or -x here?
This was from a couple of days ago, old ntpdate/adjtime crap, I was just trying to document all progress :-/ ....
Apr 3 22:04:51 rpi ntpd[3003]: proto: precision = 4.020 usec (-18) Apr 3 22:04:51 rpi ntpd[3003]: Listen and drop on 0 v6wildcard [::]:123 Apr 3 22:04:51 rpi ntpd[3003]: Listen and drop on 1 v4wildcard 0.0.0.0:123 Apr 3 22:04:51 rpi ntpd[3003]: Listen normally on 2 usmsc0 [fe80::ba27:ebff:fe2b:abcc%1]:123 Apr 3 22:04:51 rpi ntpd[3003]: Listen normally on 3 usmsc0 192.168.0.1:123 Apr 3 22:04:51 rpi ntpd[3003]: Listen normally on 4 lo0 [::1]:123 Apr 3 22:04:51 rpi ntpd[3003]: Listen normally on 5 lo0 [fe80::1%2]:123 Apr 3 22:04:51 rpi ntpd[3003]: Listen normally on 6 lo0 127.0.0.1:123 Apr 3 22:04:51 rpi ntpd[3003]: Listening on routing socket on fd #27 for interface updates Apr 3 22:04:51 rpi ntpd[3003]: restrict default: KOD does nothing without LIMITED. Apr 4 22:00:01 rpi syslogd[555]: restart Apr 5 22:00:00 rpi syslogd[555]: restart Apr 6 00:09:02 rpi ntpd[3003]: ntpd exiting on signal 15 (Terminated) Apr 5 19:15:17 rpi ntpd[3335]: ntpd 4.2.8-o Fri Dec 19 21:49:44 EST 2014 (import): Starting Apr 5 19:15:17 rpi ntpd[3335]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -ggggxNow I do.Apr 5 19:15:18 rpi ntpd[5526]: proto: precision = 4.020 usec (-18) Apr 5 19:15:18 rpi ntpd[5526]: Listen and drop on 0 v6wildcard [::]:123 Apr 5 19:15:18 rpi ntpd[5526]: Listen and drop on 1 v4wildcard 0.0.0.0:123You don't seem to be listening to anything outside your network.Apr 5 19:15:18 rpi ntpd[5526]: Listen normally on 2 usmsc0 [fe80::ba27:ebff:fe2b:abcc%1]:123 Apr 5 19:15:18 rpi ntpd[5526]: Listen normally on 3 usmsc0 192.168.0.1:123 Apr 5 19:15:18 rpi ntpd[5526]: Listen normally on 4 lo0 [::1]:123 Apr 5 19:15:18 rpi ntpd[5526]: Listen normally on 5 lo0 [fe80::1%2]:123 Apr 5 19:15:18 rpi ntpd[5526]: Listen normally on 6 lo0 127.0.0.1:123 Apr 5 19:15:18 rpi ntpd[5526]: Listening on routing socket on fd #27 for interface updates Apr 5 19:15:18 rpi ntpd[5526]: restrict default: KOD does nothingYou have a kod line without limited.
Yeah, straight out of stock config file ....
without LIMITED. Apr 6 07:29:48 rpi ntpd[9356]: ntpd 4.2.8-o Fri Dec 19 21:49:44 EST 2014 (import): Starting Apr 6 07:29:48 rpi ntpd[9356]: Command line: ntpd -qThis is probably an accident.
No, this was me trying to manually set the time this A.M. ....
Apr 6 07:29:49 rpi ntpd[9356]: proto: precision = 4.020 usec (-18) Apr 6 07:29:49 rpi ntpd[9356]: unable to bind to wildcard address :: - another process may be running - EXITING The 1st invocation, on Apr 3, was in original configuration, undisciplined local clock only & me using ntpdate/adjtime to munge time. The second invocaztion was yesterday w/ my ISP as the 1st server, undisciplined local clock as backup (last server listed). I see nomention of my ISP's time server, & time is not getting kept correctly. I tried a manual update this A.M., as seen, w/ no effect. Pilot error, I suspect, any ideas ? Thanks & TIA ....I would add kod limited to make the warning go away. I would also fix my config to listen to packets from the outside. christos
The kmod line is from box-stock config (BTW), I will add limited as recommended.
I thought I had fixed my config :-) .... I have my ISP's time server set as server, what else do I need to do ?
--
William A. Mahaffey III
----------------------------------------------------------------------
"The M1 Garand is without doubt the finest implement of war
ever devised by man."
-- Gen. George S. Patton Jr.