From owner-freebsd-current@FreeBSD.ORG Tue Nov 11 20:18:09 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9796D26B; Tue, 11 Nov 2014 20:18:09 +0000 (UTC) Received: from mail-in4.apple.com (mail-out4.apple.com [17.151.62.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6AEF57CC; Tue, 11 Nov 2014 20:18:08 +0000 (UTC) Received: from relay3.apple.com (relay3.apple.com [17.128.113.83]) by mail-in4.apple.com (Apple Secure Mail Relay) with SMTP id CC.0A.12968.00F62645; Tue, 11 Nov 2014 12:18:08 -0800 (PST) X-AuditID: 11973e12-f79306d0000032a8-ab-54626f00a996 Received: from [17.149.228.80] (Unknown_Domain [17.149.228.80]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id A9.A7.17790.50F62645; Tue, 11 Nov 2014 12:18:13 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Changing timezone without reboot/restarting each service? From: Charles Swiger In-Reply-To: <201411111357.40061.jhb@freebsd.org> Date: Tue, 11 Nov 2014 12:16:19 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <5330A42B-CBCA-4349-BE12-777401272050@mac.com> References: <5460B143.6080206@FreeBSD.org> <201411111357.40061.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1878.6) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrILMWRmVeSWpSXmKPExsUi2FAYrMuQnxRi8PS9ssWEKz+YLOa8+cBk sffIdWaL3lUbWR1YPGZ8ms8SwBjFZZOSmpNZllqkb5fAlXHyUQt7wWquihcnLzM3MM7i6GLk 5JAQMJGYN+0LM4QtJnHh3nq2LkYuDiGBvYwSV+ftZIYpuntyHyOILSTQyyTRvt8HxGYW0JK4 8e8lE4jNK2AgsWTXJrB6YQE3iQPzV7B2MXJwsAmoSUyYyAMS5hQwlHi1ZiMLiM0ioCrxvvkG E0gJs0C0xL7jRRATtSWWLXzNDDHRSuLWxXvMEFv9JXp3nWYBKRcRUJKY+k0N4jB5iQ8fjrOD XCwh8JNV4vTZNcwTGIVmITluFpLjZiFZsYCReRWjUG5iZo5uZp6JXmJBQU6qXnJ+7iZGUBhP txPawXhqldUhRgEORiUeXg3/xBAh1sSy4srcQ4zSHCxK4rxLcoBCAumJJanZqakFqUXxRaU5 qcWHGJk4OKUaGE1qlvq2TVrAUhHHtjzzsvaya6zu12NKrxp92Mn6syDnVd7v/s9lUQpzf6YY y2hP3tOq4bnWelPr6cIfBpHXk25fVUi95tt/QtFB7NuliKOzOTOnee1m6L6s+k1Mr6NEX2vq RAZOTUcZ7YDnOtfvhrrJsX3bwZpzm/FXIoM2a5XMmY7N+v+WKrEUZyQaajEXFScCAKjeI9lE AgAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUiOPVJgC5rflKIwf4/khYTrvxgspjz5gOT xd4j15kteldtZHVg8ZjxaT5LAGMUl01Kak5mWWqRvl0CV8bJRy3sBau5Kl6cvMzcwDiLo4uR k0NCwETi7sl9jBC2mMSFe+vZQGwhgV4mifb9PiA2s4CWxI1/L5lAbF4BA4kluzYxg9jCAm4S B+avYO1i5OBgE1CTmDCRByTMKWAo8WrNRhYQm0VAVeJ98w0mkBJmgWiJfceLICZqSyxb+JoZ YqKVxK2L95ghtvpL9O46zQJSLiKgJDH1mxrEYfISHz4cZ5/AyD8LyT2zkNwzC8nUBYzMqxgF ilJzEiuN9RILCnJS9ZLzczcxgsKuoTB4B+OfZVaHGAU4GJV4eDX8E0OEWBPLiitzDzFKcDAr ifAyhCWFCPGmJFZWpRblxxeV5qQWH2KU5mBREudNiI4NERJITyxJzU5NLUgtgskycXBKNTBy C1z1OiP7hp1/Zs73tUqX28+dM9Jb0/Rb7y8r+xXn45bZyyaq2z+/rxUUfVFg0qOQoEIZBvX9 Bc5W2UnyqqKbgvzZv+Z0HBZItKl8YyF8m/fmwkMud0o8fz6sFK7bd+7bEeHIrnAxS0XD7I39 x58sFU//2KrGbD/x66J4w2NWVcc3tTDosCqxFGckGmoxFxUnAgCRsTU5NwIAAA== Cc: freebsd-current@freebsd.org, lev@freebsd.org, FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Nov 2014 20:18:09 -0000 On Nov 11, 2014, at 10:57 AM, John Baldwin wrote: > On Monday, November 10, 2014 7:36:19 am Lev Serebryakov wrote: >>=20 >> After changing timezones in Russia (with replacing /etc/localtime >> with new file), I found that cron works in "old" timezone till >> restart. And all other services do the same, but cron is most obvious >> here :) >>=20 >> Looks like libc reads timezone only once and it could not be chamged >> for process without restart (which leads to, effectivly, restart of >> whole server). >>=20 >> Is it known problem? I think, it should be fixed somehow. I >> understand, that re-check timezone file on each time-related call >> could be expensive, though :( >=20 > In practice, timezone changes are very rare, so rechecking the file is > quite expensive to do. I think having to restart processes is fine = for this. In theory, timezone changes should be very rare. We've actually had about ten TZ updates in 2014; the most recent was FET = -> MSK for Belarus plus minor tweaks to IDT vs ICT. If you're working within = the scope of a single country, I suspect that one could ignore the bulk of TZ = updates and be fine most of the time. If you're world-wide, however, TZ update frequency becomes more = noticeable.... Regards, --=20 -Chuck