Date: Sun, 1 Dec 2002 01:37:27 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: Giorgos Keramidas <keramida@ceid.upatras.gr>, "Daniel C. Sobral" <dcs@tcoip.com.br>, <current@FreeBSD.ORG> Subject: Re: Problem with ntpdate Message-ID: <20021201013415.M5535-100000@gamplex.bde.org> In-Reply-To: <3DE8B803.A699D043@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 30 Nov 2002, Daniel C. Sobral wrote: > Giorgos Keramidas wrote: > > > > On 2002-11-28 17:00, "Daniel C. Sobral" <dcs@tcoip.com.br> 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 You could use the same time under FreeBSD as under Windows (local time). Then you would only have to fix the clock at most twice a year when both Windows and FreeBSD adjust it for DST. Bruce 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?20021201013415.M5535-100000>