Re: hwclock "hanging" for ~24 hours

[Tomasz Chmielewski <mangoo@xxxxxxxx>]

Karel Zak schrieb:

(...)

> >  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.

It does not "hang" anymore:

# ./hwclock --show
Timed out waiting for time change.


But still, it won't set the hardware clock so it can start ticking:

# date
Tue Aug 12 13:13:59 UTC 2008
# ./hwclock --systohc
Timed out waiting for time change.



--
Tomasz Chmielewski
http://wpkg.org
--
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