From owner-freebsd-current Thu Nov 28 11:27:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7834E37B401 for ; Thu, 28 Nov 2002 11:27:46 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 895A143EA9 for ; Thu, 28 Nov 2002 11:27:44 -0800 (PST) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id gASJRgV06002 for ; Thu, 28 Nov 2002 17:27:42 -0200 Message-ID: <3DE66E2E.7050201@tcoip.com.br> Date: Thu, 28 Nov 2002 17:27:42 -0200 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021125 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Problem with ntpdate References: <3DE667DF.9060200@tcoip.com.br> In-Reply-To: <3DE667DF.9060200@tcoip.com.br> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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