On Sat, Aug 09, 2008 at 05:05:23PM +0200, Tomasz Chmielewski wrote:
> Karel Zak schrieb:
>
> (...)
>
>>> But would it solve the issue, really?
>>
>> Yes, that's core of the problem. But we also need to remove some return
>> code checks from manipulate_clock(). These checks are unnecessary,
>> because there is hclock_valid boolean... (this is my bug.)
>>
>>> hwclock from busybox is able to show the clock (Tue Nov 30 00:00:00
>>> 1999 0.000000) and also set it; the above seems to exit only - and
>>> still, we're not able to show or set the clock?
>>
>> I'll send a patch ASAP.
>
> Could you notify the list when the patch is ready, please?
The patch is below. It's based on gettimeofday() rather than on
SIGALRM (alarm(2)). The gettimeofday has some overhead, but it
shouldn't be a big problem for the synchronization function (... and
it's fallback for systems without RTC_UIE_ON).
Please, test & review. I'd like to use the patch in 2.14.1.
Karel
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
