> Are you sure that drift factor (re)calculation does not happen if > writing the Hardware Clock fails? I just had a quick look at the > code and it seem that we do not test to see if write fails. So > (re)calculation might work as is? It does not seem to work the obvious way: > [root@localhost ~]# date > Thu Oct 9 14:56:30 UTC 2014 > [root@localhost ~]# hwclock --systohc --update > hwclock: ioctl(RTC_SET_TIME) to /dev/rtc to set the time failed.: Invalid argument > [root@localhost ~]# hwclock --get > Thu Jan 8 05:12:51 1970 .543449 seconds I will try to look into it. -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
