> On Nov 23, 2017, at 9:29 AM, Rodney W. Grimes > <[email protected]> wrote: > > [ Charset UTF-8 unsupported, converting... ] >> On Thu, Nov 23, 2017 at 7:17 AM, Rodney W. Grimes >> <[email protected]> wrote: >>>> Also we do provide an ntp.conf so ... >>> >>> We do, a template, all commented out, and does not work for >>> machines behind strong firewalls that wont allow ntp out >>> to the net but have internal ntp servers that are used for >>> such things. >>> >>> Well maybe not all commented out, I think it defaults to >>> some public pools. I believe it would be missing iburst >>> for use with ntp -pg >> >> Does ntpdate work out of the box in such environments? If so, how? > > ntpdate time.nist.gov > > ntpdate does not need a configureration file, just a command > line argument. > >
At the banks we used to rely on both (in this order) ntpdate running and then ntpd running. Running ntpdate before ntpd meant that on a [re]boot, ntpdate would jump the box to the appropriate time, regardless of how far behind the clock was (think "dead cmos battery" on a system left powered-off for a long time). Meanwhile, running ntpd *without* the sync-on-start feature meant we could bounce the ntpd service as necessary and it would always adhere to the limit we set on it -- one hour to prevent syncing on systems which had been manually adjusted by greater than an hour for some one-off instances. -- Devin _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "[email protected]"
