From owner-freebsd-current@freebsd.org Tue Aug 8 06:35:03 2017 Return-Path: Delivered-To: freebsd-current@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 E1549DC5907 for ; Tue, 8 Aug 2017 06:35:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B07E971D7B; Tue, 8 Aug 2017 06:35:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-pg0-x22e.google.com with SMTP id l64so10960559pge.5; Mon, 07 Aug 2017 23:35:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=WPt3QTOSNMs7IIzdYfqWgNwBJjuX2A6oYP4yjKC8aog=; b=Yp5uJccTOfkThGfPX99dZ/EkMUCVlqrlhiMui/eh2DKNapqI7LMjhTPbwFH4smwBxs l3oglBjIOT+6JH1G6QjV8mLy55hqH/SCdNhe2pSp/MrqwA68SZGvv60z0/PKNUv4hRQ+ Ct6N53ZkJV6KfDvgaTkv2AMKy8vCBR/h6brJCUx1f2NV1RHGkjLbGf1nPBGBzcwVCe9g Sd2kwEAkF9aoj8zWRrHLaNwFdmL10mTqIwo0+4kS2G0OrvQbnG/F1JN3HGe+7N5xDf4S CNoP9GYtVf7WJOtYN39qZ5hEYiIdtmYEVy+wiwBcXCASaUIJ6UYx6zlWJoQ+2s7bPZDh M/GA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=WPt3QTOSNMs7IIzdYfqWgNwBJjuX2A6oYP4yjKC8aog=; b=DXuIL+vMW7t4lERaAC7AFJ9BqfK/veTcVbarlVTi6/fRdUQ20JQqzUxCE5Z5pKVmdd ANmF9l0Tv30jj7MyrstYuV1baAZarEkufP/dwYKxdqSzfysZwbS7CRArhY6ZjuNBKVvg YGoR5R3uQ+dJBEwpltWBp2HZlIEZ2VKd2hPDLWpQ4E/stPxN9xR9ZV7UR6+TAIJkIwiv zi4x+aMgobZF5lNahYUEJBWAjNgVmwVgAp5VhyBOKYFbOc1ZWMCLGLYDdFYT+RbpDUhx 58nvWVOwqF6VhJVezSu12G1o3E8fV02qnG3YMN6vx8vuflUba1AOZRsknGjxRQ0Q47KJ k8zw== X-Gm-Message-State: AHYfb5i+htiMbrIPKTfdY4UWdcLdxUT8B1Qn443k46NDdhf+8hB4wQaW 3iPyDNg4mFRyGn+AGUvAFETUHLxpcbX7XMo= X-Received: by 10.84.167.2 with SMTP id c2mr3549505plb.370.1502174103006; Mon, 07 Aug 2017 23:35:03 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.100.165.42 with HTTP; Mon, 7 Aug 2017 23:35:02 -0700 (PDT) In-Reply-To: <20170807214811.GP20729@alchemy.franken.de> References: <20170807214811.GP20729@alchemy.franken.de> From: Kevin Oberman Date: Mon, 7 Aug 2017 23:35:02 -0700 X-Google-Sender-Auth: X-nt-ihSdMgNyPvtZlf9QFT28bA Message-ID: Subject: Re: [tzsetup] can't set up local timezone if CMOS is set to UTC To: Marius Strobl Cc: Boris Samorodov , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 06:35:04 -0000 On Mon, Aug 7, 2017 at 2:48 PM, Marius Strobl wrote: > On Mon, Aug 07, 2017 at 09:51:15AM +0300, Boris Samorodov wrote: > > 07.08.2017 09:44, Boris Samorodov ?????: > > > Hi Marius, All, > > > > > > Subj at today's amd64-HEAD. If I use command "sudo tzsetup" and > > > choose YES (CMOS clock is set to UTC), the program just quits. > > > Yea, my clocks are at UTC but I want to get time at local timezone. :-) > > > > > > I've found a recent commit to tzsetup, is it the cause? > > > > Hm. There is a log message at r322097: > > --- > > - Make the initial UTC dialog actually work by giving the relevant files > > the necessary treatment and then exit when choosing "Yes" there > instead > > of moving on to the time zone menu regardless. > > --- > > > > I must misunderstand something. > > > > So my question is: how to set up local time zone if CMOS is set to UTC? > > Yeah, I hadn't thought of the case where one would like to set up > a configuration in which the RTC is using UTC but the timezone is > not. So I've reverted the corresponding part of r322097 for now as > I don't see an obvious way to give /etc/wall_cmos_clock appropriate > treatment in all 3 relevant cases (UTC/UTC, !UTC/UTC and !UTC/!UTC > regarding RTC/timezone) for all interactive and non-interactive > ways of using tzsetup(8). > > Marius Thanks for the quick fix, Marius. FWIW, it the system is not running Windows (dual boot), it has long been standard BSD practice to set the RTC to UTC and then set the timezone to local time. I've seen this back to the days of at least BSD4.3 (NOT FreeBSD) but 20 or more years ago. I have worked at two places with hundreds of systems, all running this way, including all of "my" systems. The practice of setting RTC on Unix-only platforms to local time really started with dual-boot systems, especially Windows. (I first saw this on a BSD Unix/VMS dual boot system.) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683