Default behaviour is that if the time zone is off by more than a preset amount (I think 128ms) it will refuse to sync, and silently fails.
Read the docs for the config file command "tinker panic 0" (and its implications) which will remove the limitation and allow stepping to the new time. Also ntpd can be started with the -g arg to get the same effect. BillK On Wed, 2006-02-01 at 19:25 +0000, James wrote: > Devon Miller <devon.c.miller <at> gmail.com> writes: > > > Make sure you have told you firewall to allow port 123 for both TCP & > > UDP.I had the same behavior until I did that.dcm > > Well my firewall should allow outgoing initiated sessions from the > ntpd (internal) server. From what I read, the remote ntpd server > does not initiate communications, it my server that initates the > communications? > > That assumed, my firewall rules (which are undergoing revision) are ok? > > OK, I'm new to ntpd, but it looks straightforward. > > after emerging, I started up ntpd and added it to the default run level. > Then I checked and got: > > ntpq -p > remote refid st t when poll reach delay offset jitter > ============================================================================== > ecoca.eed.usv.r 80.96.120.253 2 u 8 64 1 202.639 1436722 0.001 > > then: > # date > Wed Feb 1 14:58:04 Local time zone must be set--see zic manual page 2006 > > > /etc/localtime is a lock file so where do I correct/set the time zone to > EST (eastern standard time) so ntpd will see it can correct my actual time > (it's off by a little more than (1) hour. > > But now when I run 'ntpq -p' I get: > ntpq: read: Connection refused > > What did I mess up or miss? > > > James > > > > > > > > man zic and man ntpd did not help, or I missed the file to edit or the > correct command syntax.... > > James > > > -- gentoo-user@gentoo.org mailing list
