Date: Wed, 16 Jul 2014 09:15:05 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Isaac Dunham <ibid.ag@gmail.com>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] hwclock restoring time wrong
Message-ID: <20140716091505.21a8c1f7@ncopa-desktop.alpinelinux.org>
In-Reply-To: <20140716111243.GA2021@newbook>
References: <20140716111243.GA2021@newbook>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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.

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---