Date: Tue, 11 Nov 2014 12:16:19 -0800 From: Charles Swiger <cswiger@mac.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org, lev@freebsd.org, FreeBSD Current <current@freebsd.org> Subject: Re: Changing timezone without reboot/restarting each service? Message-ID: <5330A42B-CBCA-4349-BE12-777401272050@mac.com> In-Reply-To: <201411111357.40061.jhb@freebsd.org> References: <5460B143.6080206@FreeBSD.org> <201411111357.40061.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 11, 2014, at 10:57 AM, John Baldwin <jhb@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5330A42B-CBCA-4349-BE12-777401272050>