[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [alpine-devel] hwclock restoring time wrong
From:       Isaac Dunham <ibid.ag () gmail ! com>
Date:       2014-07-19 14:13:41
Message-ID: 20140719141340.GA2042 () newbook
[Download RAW message or body]

On Wed, Jul 16, 2014 at 09:15:05AM +0200, Natanael Copa wrote:
> On Wed, 16 Jul 2014 04:12:44 -0700
> Isaac Dunham <ibid.ag@gmail.com> wrote:
> 
> > Hello,
> > I've encountered a problem that seems to throw cron for a loop:
> > hwclock is saving the UTC time, but restoring it as if it were localtime.
> > 
> > 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.

Thanks,
Isaac Dunham
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]