Date: Wed, 30 Jul 2014 09:59:46 +0200
From: Igor Falcomata' <lists@cioccolatai.it>
To: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] hwclock restoring time wrong
Message-ID: <20140730075945.GJ27179@127.0.0.1>
References: <20140716111243.GA2021@newbook>
 <20140716091505.21a8c1f7@ncopa-desktop.alpinelinux.org>
 <20140719141340.GA2042@newbook>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140719141340.GA2042@newbook>

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@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---