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: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Outros:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
