Date: Thu, 28 Nov 2002 23:30:25 +0000 (GMT) From: Daniel Flickinger <attila@hun.org> To: Daniel C.Sobral <dcs@tcoip.com.br> Cc: FreeBSD-CURRENT <current@freebsd.org> Subject: Re: Problem with ntpdate Message-ID: <20021128233025.gkyY5725@hun.org> In-Reply-To: <3DE66E2E.7050201@tcoip.com.br> References: <3DE667DF.9060200@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
If, as you state, the time is off two hours due to
Windows, ntpd has a time correction limitation of 1000
secs which can be overridden one time only by specifying
the -g option; the man page for ntpdate does not say,
and there is no -g option equivalent. check the source
for the limitation.
However, your log report shows that neithr nptdate nor
ntpd are connecting to the network with the obvious
result. Suggest maybe you list your possible time
servers in ntpd's NetInfo data. A second possibility is
that ntpdate is trying to make a conection before the
network line is up and live --this is particularly true
with ppp dial ups and non-static ADSL lines. In that
case, use the /etc/ppp.linkup file to call the final
network setup, ntpdate, etc.
Sent: Thu, 28 Nov 2002 17:27:42 -0200 by Daniel C. Sobral
| More information:
|
| ntpdate_flags="-s -b clock.tcoip.com.br":
|
| Nov 28 15:13:31 dcs ntpdate[259]: no server suitable for synchronization
| found
|
| ntpdate_flags="-s -b 200.220.255.229":
|
| Nov 28 15:15:38 dcs ntpdate[259]: no server suitable for synchronization
| found
| Nov 28 15:15:39 dcs ntpd[377]: ntpd 4.1.1b-a Thu Nov 28 11:09:29 BRST
| 2002 (1)
| Nov 28 15:15:39 dcs ntpd[377]: kernel time discipline status 2040
| Nov 28 15:15:50 dcs ntpd[377]: sendto(200.220.255.229): No route to host
|
| That is, the extra time taken NOT resolving clock.tcoip.com.br was,
| apparently, enough for something in the IP stack to go up.
|
| This looks, after all, like a more serious bug than I first assumed.
|
| Daniel C. Sobral wrote:
|
| > I found out that ntpdate just doesn't seem to be working at all during
| > boot. Ntpd dies because of the time differential (windows changes the
| > time two hours because of the TZ). No message from ntpdate (I'll next
| > try to divert it to syslog).
| >
| > Running *after* boot, by typing /etc/rc.d/ntpdate start, works fine.
| >
| > I tried no ntpdate_flags, ntpdate_flags="-b server.name", and
| > ntpdate_flags="server.name".
| >
| > Suggestions?
| >
|
|
| --
| Daniel C. Sobral (8-DCS)
| Gerencia de Operacoes
| Divisao de Comunicacao de Dados
| Coordenacao de Seguranca
| TCO
| Fones: 55-61-313-7654/Cel: 55-61-9618-0904
| E-mail: Daniel.Capo@tco.net.br
| Daniel.Sobral@tcoip.com.br
| dcs@tcoip.com.br
|
| Outros:
| dcs@newsguy.com
| dcs@freebsd.org
| capo@notorious.bsdconspiracy.net
|
| Dying is a very dull, dreary affair. My advice to you is to have
| nothing whatever to do with it.
| -- W. Somerset Maughm, his last words
|
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021128233025.gkyY5725>