From owner-freebsd-arch Mon Jun 4 19: 2:41 2001 Delivered-To: freebsd-arch@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A41F437B406 for ; Mon, 4 Jun 2001 19:02:39 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f5522Z434463; Mon, 4 Jun 2001 19:02:35 -0700 (PDT) (envelope-from dillon) Date: Mon, 4 Jun 2001 19:02:35 -0700 (PDT) From: Matt Dillon Message-Id: <200106050202.f5522Z434463@earth.backplane.com> To: huntting@glarp.com Cc: freebsd-arch@FreeBSD.ORG Subject: Re: changing timezones References: <200106042325.f54NPoL77213@hunkular.glarp.com> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :When /etc/localtime changes (because the machine moves to a different :timezone), how is one supposed keep up on current temporal events? : :I get the feeling tzset() and tzsetwall() should be checking to :see if the timezone has changed since they were last called (they :dont currently). : :Any thoughts? : :brad Well, you definitely don't want to rip the current timezone out from under a running program. That could lead to a mess. I do occassionally notice timezone issues from long running programs such as sendmail and syslogd when I've forgotten to set the timezone in a new install, but I usually just reboot to ensure that everything has started from a clean slate. It is also fairly easily to simply restart the effected servers. I'm not sure an automated solution is really desireable. Timezones generally never change except maybe on a laptop and laptops get powered up and down all the time anyway. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message