From owner-freebsd-stable Tue Oct 31 2: 9:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vivaldi.pn.npi.msu.ru (gw.pn.npi.msu.ru [193.232.127.202]) by hub.freebsd.org (Postfix) with ESMTP id BC63537B4CF for ; Tue, 31 Oct 2000 02:09:09 -0800 (PST) Received: from handel.pn.sinp.msu.ru (handel.pn.npi.msu.ru [195.208.223.24]) (authenticated) by vivaldi.pn.npi.msu.ru (8.11.1/8.11.1) with ESMTP id e9VA58b40505; Tue, 31 Oct 2000 13:05:08 +0300 (MSK) (envelope-from svysh@pn.sinp.msu.ru) Message-Id: <4.3.2.7.2.20001031130256.00aa3260@vivaldi> X-Sender: svysh@vivaldi (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 31 Oct 2000 13:08:09 +0300 To: Max Khon , "Alexandr A. Listopad" From: Sergei Vyshenski Subject: Re: no switching to standard time Cc: freebsd-stable@FreeBSD.org In-Reply-To: References: <20001031092357.A85859@atom.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CMOS clock is set to UTC. The output of "date" did not switched to standard local time. Is it a predefined feature? Shall I expect automatic switching only with cmos clock set to local time? At 12:48 31.10.00 +0600, Max Khon wrote: >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