From owner-freebsd-questions@freebsd.org Mon Oct 31 07:52:25 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70C76C2741D for ; Mon, 31 Oct 2016 07:52:25 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0289710B9 for ; Mon, 31 Oct 2016 07:52:25 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:1c1d:86a1:a200:b700]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id E414E19B7 for ; Mon, 31 Oct 2016 07:52:19 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/E414E19B7; dkim=none; dkim-atps=neutral Subject: Re: return from DST did not worked To: freebsd-questions@freebsd.org References: <20161030212001.GA4467@c720-r292778-amd64> <20161031010217.79915167@gumby.homeunix.com> From: Matthew Seaman Message-ID: <77d41784-51d5-de96-afc8-ad517ab2d2ee@FreeBSD.org> Date: Mon, 31 Oct 2016 07:51:58 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161031010217.79915167@gumby.homeunix.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TAlwKHqwcbF1vpugAqBEcSl5I2Xp0qlg9" X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2016 07:52:25 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TAlwKHqwcbF1vpugAqBEcSl5I2Xp0qlg9 Content-Type: multipart/mixed; boundary="OFpwmuPf2JrP266XiHjdv8bw6Kd519Jn5"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <77d41784-51d5-de96-afc8-ad517ab2d2ee@FreeBSD.org> Subject: Re: return from DST did not worked References: <20161030212001.GA4467@c720-r292778-amd64> <20161031010217.79915167@gumby.homeunix.com> In-Reply-To: <20161031010217.79915167@gumby.homeunix.com> --OFpwmuPf2JrP266XiHjdv8bw6Kd519Jn5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 31/10/2016 01:02, RW via freebsd-questions wrote: > On Sun, 30 Oct 2016 22:20:01 +0100 > Matthias Apitz wrote: >=20 >> Hello, >> >> We in Europe returned this night from DST CEST. In the night, when my >> system FreeBSD 11.0-CURRENT r292778 (amd64) >> was down, all the clocks were set back from 03:00 (CEST) to 02:00 >> (CET). When I booted my system the date(1) command was showing >> correctly string 'CET' but the wrong hour, still the one hour ahead, >> until I run ntpdate(8), >=20 > Do you keep your bios/cmos clock set to local time? The installer > creates a file /etc/wall_cmos_clock as a flag if you set it up this way= =2E >=20 > The normal setup is to keep the bios clock on UTC, and then FreeBSD > works out the local time - including DST. But if you run on local time > I don't think FreeBSD handles DST in the cmos clock because that mode > is intended for dual-booting. Matthias is correct that having the BIOS clock a.k.a. the CMOS clock running UTC is the preferred setting, but even if you don't the system will still track daylight savings time changes for you. There's a cronjob in /etc/crontab that runs adjkerntz(8). That should get run every half hour between midnight and 5.00am each night, which will detect that it needs to update the CMOS clock on the two occasions each year when the clocks change... If the OP doesn't leave his system running overnight, then that will not happen, and the time will get set an hour out on reboot in the morning. If this is what happened, then it should suffice to set the kernel clock to the correct time (ie. turn off ntpd(8), use date(1) to get the clock within a few seconds of correct, start ntpd(8) and leave it to synch properly, then run 'adjkerntz -a') adjkerntz(8) also should get run as a daemon at system boot if your system is set to use local CMOS time, which sets the kernel clock from the CMOS clock at bootup, and sets the CMOS clock from the kernel clock on shutdown. Cheers, Matthew --OFpwmuPf2JrP266XiHjdv8bw6Kd519Jn5-- --TAlwKHqwcbF1vpugAqBEcSl5I2Xp0qlg9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJYFvgsXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATtmYP/R1jG8fXZR2lznA+4iWe40Hy p3k4y4n9Pp8+cSFjvW9YEddezEJtG8sRMrWqEeDAQAG0zlA/oHfs6QIfqvgFNQEc DLO9sDX7yF+eSETvd+MHQABn7EeMfyl+ZCC7kZ8Me32rOnO1jT9WUd6Ks05Nhskl ZWLNcLZ+5yAvFZcQcwzO7DyOMSY70uElLe+78WaJ+ZM1njG21rS65AZ//w8Te50+ aTMBIDxKEAoXbZAbqqISu1bv0MsjBr264Gq/CH1j1KgI/tbrrxGkn3w3Nr27GXGg qCP9eUjYd5R+FZRG026N4ybM5lvNNdDTnDMfVgQx7qNXsZfnUZmKWeb0moo3Sgak kcrAbkpO12Qh/q8znXyYNjLhyBR8XiFzRO9zEjeDHNYubVOoE7ZkDKDE+f+PL4d8 4rwwqeeSkmb/yS0D5SxSYo27agxpo2C8DiKtwtU5Bxy8by5gMHGgITQrLlA/CRtE MDQW5N8v67Zak9I+OFXey9tQP0M8BZUZheMX8l4hrWUC93Wm2bjGwQCMYRiGW2OC PGN5xWl4mqL4sbysaXAe4efvMlV5pYjSN0DAuRPKoMEy+b/MY44nx7/eYdcoICMk T8jV6hW2elrzy3XQ8n+67UzVkDq/V4piRgxPU/oAkz8LQHzitNi8FE+OicJ0APQk 4fcSgCpPYuuQ5lfLwk50 =MPVO -----END PGP SIGNATURE----- --TAlwKHqwcbF1vpugAqBEcSl5I2Xp0qlg9--