Date: Mon, 28 Mar 2011 14:28:03 -0400 From: Brian Reichert <reichert@numachi.com> To: Garrett Cooper <gcooper@FreeBSD.org> Cc: hackers@freebsd.org, dieterbsd@engineer.com Subject: Re: Keeping /etc/localtime up-to-date Message-ID: <20110328182803.GF86409@numachi.com> In-Reply-To: <AANLkTim3Axh4FV8oCJSoBYHJEq4=XkhfNjPAxkH9sV-2@mail.gmail.com> References: <8CDBB88B5271976-11D4-322B@web-mmc-d02.sysops.aol.com> <AANLkTim3Axh4FV8oCJSoBYHJEq4=XkhfNjPAxkH9sV-2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 28, 2011 at 11:10:42AM -0700, Garrett Cooper wrote: > On Mon, Mar 28, 2011 at 10:57 AM, <dieterbsd@engineer.com> wrote: > > I have been running FreeBSD and NetBSD with /etc/localtime being > > a symlink for years and have not seen any problems as a result. > > +1. Many Linux distros do the same thing as well (Gentoo is just one example). RedHat is a counter-example. Parts of the kernel are not timezone aware, and seem to be hard-coded to use whatever TZ the hardware clock is in. The symptom I was running into was that the kernel's timestamps were waffling back-and-forth during the boot process. I was making use of a symlink, but the timezone data was on a different partition from the root parition. RedHat's support officially said "don't use a symlink", as any process started before the 'real' TZ files were available would reckon time differently when printing timestamps. Lots of people got bit by this: https://bugzilla.redhat.com/show_bug.cgi?id=91228 YMMV. > Thanks, > -Garrett > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Brian Reichert <reichert@numachi.com> BSD admin/developer at large
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110328182803.GF86409>