Timezones and date (GMT to BST)

[Gary Allan <dragonfly@xxxxxxxxxxxxxxx>]

Joerg Sonnenberger wrote:
> On Sat, Mar 26, 2005 at 02:50:12AM +0000, Pawel Biernacki wrote:
>
> > Dnia 14.03.2005 Joerg Sonnenberger <joerg@xxxxxxxxxxxxxxxxxxxxxxx> 
napisa?/a:
> > > joerg       2005/03/14 15:55:41 PST
> > >
> > > DragonFly src repository
> > >
> > >  Modified files:
> > >    bin/date             date.c
> > >  Log:
> > >  Instead of using the non-standard conforming %+ format string,
> > >  use nl_langinfo to query the default format string.
> > >
> > >  Revision  Changes    Path
> > >  1.9       +2 -1      src/bin/date/date.c
> > >
> > >
> > > http://www.dragonflybsd.org/cvsweb/src/bin/date/date.c.diff?r1=1.8&r2=1.9&f=u
> >
> > this commit totaly destroy any imformation about local time zone.
> > e.g.
> >
> > apocalypse# date
> > Sat Mar 26 03:49:13 2005
> > apocalypse# ./date.old
> > Sat Mar 26 03:49:14 CET 2005
> >
> > is there are any plans to make it work again? (mayby after final CITRUS
> > integration?)
>
>
> This is _not_ a bug in date, I think the locale is wrong here. But I have
> to check this.
>
> Joerg

Hello,

I am also seeing this behavior in date(1)

> date
Sun Mar 27 15:46:00 2005

This morning I have had to manually correct the system clock for BST. I
selected the correct timezone information during installation.

Running "killall ntpd && ntpd -s" did not correctly adjust the clock.

Running "rdate -n time.windows.com" did correctly adjust the clock.
However this lead to the system displayed date and the CMOS clock (Date
displayed in BIOS) being set to BST (GMT+1). Unless /etc/wall_cmos_clock
exists the CMOS clock should always store UTC (GMT) time.

Running tzsetup did not resolve the problem so I manually copied
/usr/share/zoneinfo/Europe/London to /etc/localtime and ran adjkerntz
-a. The system is now displaying BST and the CMOS clock is storing UTC
(GMT) time. Unfortunately date(1) is still not displaying the current
timezone information.

I'm very confused as to exactly what the problem is. This only affected
the machines running DragonFly.

Regards

Gary