Date: 29 Nov 2002 09:22:13 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: current@FreeBSD.ORG Subject: Re: Problem with ntpdate Message-ID: <1038523933.21586.2.camel@chowder.gsoft.com.au> In-Reply-To: <3DE66E2E.7050201@tcoip.com.br> References: <3DE667DF.9060200@tcoip.com.br> <3DE66E2E.7050201@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2002-11-29 at 05:57, Daniel C. Sobral wrote: > 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. You could try running FreeBSD so that it thinks the CMOS clock is local time the same as windows does.. Have you tried ntpdate debugging? ntptrace can be handy too.. (Although if it works after boot then probably not) I see the 'no route to host message' given by ntpd - perhaps some routes aren't set when ntpdate runs? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 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?1038523933.21586.2.camel>