From owner-freebsd-arch Mon Jun 4 19:50:21 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 F17C737B405; Mon, 4 Jun 2001 19:50:19 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f552oJC34814; Mon, 4 Jun 2001 19:50:19 -0700 (PDT) (envelope-from dillon) Date: Mon, 4 Jun 2001 19:50:19 -0700 (PDT) From: Matt Dillon Message-Id: <200106050250.f552oJC34814@earth.backplane.com> To: Greg Lehey Cc: "Daniel O'Connor" , freebsd-arch@FreeBSD.org, huntting@glarp.com Subject: Re: changing timezones References: <200106050208.f5528eR34540@earth.backplane.com> <20010605115450.N95379@wantadilla.lemis.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 :I still don't understand what you're saying about programs not liking :the time zone changing from under them. Typically any program which :uses time zones will access /etc/timezone once only. It remains stuck :in that time zone. That may be a nuisance (I find it annoying with :syslogd, for example, but kill -1 will fix that). I frequently fly :transpacific without rebooting, but change through all time zones :where I stop over. I've never had any problems. : :Greg I think you missed the original article. The idea was to try to have a running programming automatically detect the timezone change and adjust its internal state accordingly. Doing that automatically without the programming knowing isn't a good idea. Adding code to sendmail, syslogd, cron, etc... to detect the change at a safe point, on the otherhand, might be interesting. But, ultimately, I think it would be kind of a waste of programming hours to do. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message