Summary: | sys-apps/util-linux-2.26.2 incorrect system time from rtc with clock="local" and hctosys | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Navar <navar774> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | UNCONFIRMED --- | ||
Severity: | major | CC: | floppym |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Navar
2015-10-12 23:04:34 UTC
This is probably due to a bad value in /etc/adjtime, combined with a change in hwclock behavior. Can you provide the /etc/adjtime file from your affected systems? Util-linux 2.26 Release Notes ============================= The command hwclock(8) uses the drift correction for all relevant operations and it is unnecessary to specify --adjust on the hwclock command line now. The command hwclock(8) does not automatically (re)calculate the drift factor on --systohc to avoid several problems (ntpd with '11 minute mode', for example), but the new command-line option --update-drift has to be explicitly used to force hwclock(8) to update /etc/adjtime. For more details see the hwclock(8) man page. Thanks, I see that now after grepping through the various 2.26.* release files. I see a reference after the fact in the man page as well. I noticed a flag var $clock_adjfile in /etc/init.d/hwclock that isn't referenced in my copy of /etc/conf.d/hwclock, so I just renamed the default /etc/adjtime after a re-emerge of sys-apps/util-linux-2.26.2 and a reboot. Time and date seem fine after that. Maybe a slight adjustment to /etc/conf.d/hwclock in openrc to indicate? Or maybe just a postinst note for sys-apps/util-linux. Here's the prior Dec 22 2012 /etc/adjtime from the amd64 system: 9679.784197 1356224253 0.000000 1356224253 UTC |