5 messages in org.freebsd.freebsd-stableRe: no switching to standard time| From | Sent On | Attachments |
|---|---|---|
| Sergei Vyshenski | Oct 30, 2000 2:38 pm | |
| Alexandr A. Listopad | Oct 30, 2000 10:23 pm | |
| Max Khon | Oct 30, 2000 10:48 pm | |
| Alexandr A. Listopad | Oct 30, 2000 11:38 pm | |
| Sergei Vyshenski | Oct 31, 2000 2:07 am |
| Subject: | Re: no switching to standard time | |
|---|---|---|
| From: | Sergei Vyshenski (svy...@pn.sinp.msu.ru) | |
| Date: | Oct 31, 2000 2:07:47 am | |
| List: | org.freebsd.freebsd-stable | |
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 majo...@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message