From owner-freebsd-current@freebsd.org Tue Aug 8 11:12:41 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 D3FBADD442C for ; Tue, 8 Aug 2017 11:12:41 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward100o.mail.yandex.net (forward100o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::600]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 856428041F; Tue, 8 Aug 2017 11:12:41 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback14j.mail.yandex.net (mxback14j.mail.yandex.net [IPv6:2a02:6b8:0:1619::90]) by forward100o.mail.yandex.net (Yandex) with ESMTP id DBEA72A20EE2; Tue, 8 Aug 2017 14:12:35 +0300 (MSK) Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [2a02:6b8:0:1619::15:6]) by mxback14j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 6M7eq2ZHKd-CZw02TvG; Tue, 08 Aug 2017 14:12:35 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1502190755; bh=ey2pw0oHDZ/TW/CF77XkQ/ub6gRqbm8X7Po3CuEdejk=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=cgPAfiK6rmMw+1TjBQ4zZLuF8huUlBxyLxGSODRX7SwBsz91mtCtsgnmvRW38qMY9 I0wqoTm1hERcif0w3Sy50WcO3/LHGfG/C1pKFMX2YIFnICrJ0rfXOePsET0qhKS0Cl qFUR6/eI9Z//5P3BIBCi2zoRPz2wilKGcz7O+nTo= Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id DcRKVcZop2-CZf4S7tH; Tue, 08 Aug 2017 14:12:35 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1502190755; bh=ey2pw0oHDZ/TW/CF77XkQ/ub6gRqbm8X7Po3CuEdejk=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=cgPAfiK6rmMw+1TjBQ4zZLuF8huUlBxyLxGSODRX7SwBsz91mtCtsgnmvRW38qMY9 I0wqoTm1hERcif0w3Sy50WcO3/LHGfG/C1pKFMX2YIFnICrJ0rfXOePsET0qhKS0Cl qFUR6/eI9Z//5P3BIBCi2zoRPz2wilKGcz7O+nTo= Authentication-Results: smtp4j.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: [tzsetup] can't set up local timezone if CMOS is set to UTC To: Marius Strobl Cc: freebsd-current@FreeBSD.org References: <20170807214811.GP20729@alchemy.franken.de> From: Boris Samorodov Message-ID: Date: Tue, 8 Aug 2017 14:12:34 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170807214811.GP20729@alchemy.franken.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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 11:12:41 -0000 08.08.2017 00:48, Marius Strobl пишет: > 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. I've used this configuration, well, almost forever. ;-) As Kevin has already said and my habit is to set a unix machine CMOS to UTC. > So I've reverted the corresponding part of r322097 for now Confirmed, tzsetup works as expected (at least for me). Thank you for quick fix and response. > 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). -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve