Mail archive
alpine-devel

Re: [alpine-devel] hwclock restoring time wrong

From: Igor Falcomata' <lists_at_cioccolatai.it>
Date: Wed, 30 Jul 2014 09:59:46 +0200

On Sat, Jul 19, 2014 at 07:13:41AM -0700, Isaac Dunham wrote:

> > > I determined this by setting the date manually, then running:
> > > for d in stop start; do date; hwclock -r; service hwclock $d; date; hwclock -r; done
> > > The status changes as follows:
> > >
> > > -manual localtime
> > > -real UTC hwclock
> > > hwclock stop
> > > -manual localtime
> > > -manual UTC hwclock
> > > hwclock start
> > > -localtime = manual UTC hwclock, but with the right timezone reported.
> > >
> > > I'm not sure if this is a bug in the init script or in busybox.
> > > What would be a good way to check that?
> >
> > I think the hwclock 'service' has a related configuration in /etc/conf.d/hwclock.
> >
> > I don't know if the default config is sane though.
> It seems to be sane.
>
> Per my reading, hwclock thinks it's setting UTC, so it's a bug in busybox.
> At init the boot messages say it's using UTC.

Same for me; i had to set clock="local" in /etc/conf.d/hwclock and then
works.

Of course this is a problem if the other osses you use on the same
workstations wants/are configured for the hwclock to be in UTC.

cheers,
I.


---
Unsubscribe:  alpine-devel+unsubscribe_at_lists.alpinelinux.org
Help:         alpine-devel+help_at_lists.alpinelinux.org
---
Received on Wed Jul 30 2014 - 09:59:46 UTC