From owner-freebsd-stable Mon Oct 30 22:51: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 1438D37B4C5 for ; Mon, 30 Oct 2000 22:51:02 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA21137; Tue, 31 Oct 2000 12:48:25 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 31 Oct 2000 12:48:23 +0600 (NS) From: Max Khon To: "Alexandr A. Listopad" Cc: Sergei Vyshenski , freebsd-stable@FreeBSD.org Subject: Re: no switching to standard time In-Reply-To: <20001031092357.A85859@atom.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! > > Here in Moscow, Russia, I expected the system clock > > back to standard time during the night of Oct 29, > > exactly as European tradition suggests. > > > > This did not happened by itself (the output of > > "date" was 1 hour ahead of new local time at noon > > of Oct 29.). Had to run ntpdate by hand to > > bring it 1 hour back. > > > > Is it a correct behavior? > > > > System clock here is configured to be kept as GMT and > > at the moment it shows up as a correct local time with > > "date", e.g.: > > > > Tue Oct 31 01:16:53 MSK 2000 > > I have a similar problem both in Russian (MSK) and Ukraine (EET), will > be good to correct it before 4.2-RELEASE. do you have CMOS clock set to UTC on both machines? we do not have this problem on a bunch of machines (from 3.5-STABLE to 5.0-CURRENT) with CMOS clock set to local time /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message