Hello Karel, On Thursday, June 19, 2008 at 13:35:43 +0200, Karel Zak wrote: > We can resolve the problem in userspace. I can imagine hwclock(8) that > reads /sys/class/rtc/rtc0/settime_offset_ms Yes, this sounds quite right. Do we really need a numerical value, 0 or 500? Maybe a yes/no restart_delay_flag is sufficient. I don't know enough modern (nor future) RTCs to reply for sure. If a boolean is not enough, then we should not limit to milliseconds... 32 bits are sufficient to express from -2 to +2 seconds in nanoseconds. Looks like heavy overkill, but ms are surely insuficient. The value should probably be signed: One can well imagine an RTC doing an update cycle to the just set time *after* the RTC_SET_TIME. Resulting in a small negative offset. Alain. -- 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
