From owner-freebsd-current Sat Nov 30 5: 7:57 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 286F237B401 for ; Sat, 30 Nov 2002 05:07:56 -0800 (PST) Received: from newsguy.com (smtp.newsguy.com [129.250.170.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9FDB43EB2 for ; Sat, 30 Nov 2002 05:07:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (200-163-23-099-bsace7016.dsl.telebrasilia.net.br [200.163.23.99]) by newsguy.com (8.9.1a/8.9.1) with ESMTP id FAA22046; Sat, 30 Nov 2002 05:07:15 -0800 (PST) Message-ID: <3DE8B803.A699D043@newsguy.com> Date: Sat, 30 Nov 2002 11:07:15 -0200 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Giorgos Keramidas Cc: "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: Problem with ntpdate References: <3DE667DF.9060200@tcoip.com.br> <20021129190001.GE1092@gothmog.gr> Content-Type: text/plain; charset=us-ascii 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 Giorgos Keramidas wrote: > > On 2002-11-28 17:00, "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). > > You could always fix the broken date in the CMOS setup. This will > always work, and it won't make already started processes behave in > unexpected ways because of the sudden clock change when ntpdate > changes the time :-/ What? Enter BIOS setup and fix the clock each time I alternate between Windows and FreeBSD? Just because something in the boot isn't working correctly? Now, this is just my machine, and besides my getting the lunch time wrong and seeing weird times in mail, this isn't much of an issue. But having once been responsible for mere ~35 machines, I *assure* you that either the OS Does The Right Thing during boot, or you are in for a LOT of trouble. And just to repeat, so I'm not misunderstood, the tcp changes in current might or might not be a contributing factor in my problem, but the real culprit turned out to be the network, not FreeBSD. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@linux.bsdconspiracy.net "Fundamentalist Debianites, core children of the Linuxen.... sounds like it could come from the Book of Mormon, or Tolkien on a bad day..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message