From owner-freebsd-arch Wed Jun 6 11:22:34 2001 Delivered-To: freebsd-arch@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 4231D37B401; Wed, 6 Jun 2001 11:22:32 -0700 (PDT) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f56IJjV64298; Wed, 6 Jun 2001 11:19:45 -0700 (PDT) Date: Wed, 6 Jun 2001 11:19:45 -0700 (PDT) From: Gordon Tetlow X-X-Sender: To: Matt Dillon Cc: Greg Lehey , "Daniel O'Connor" , , Subject: Re: changing timezones In-Reply-To: <200106050250.f552oJC34814@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Mon, 4 Jun 2001, Matt Dillon wrote: > 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. It would be really interesting when it came to processing your logs with a TZ shift in them as well. cron is a special case (and has been discussed ad nauseum before) as it's business is to keep track of time. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message