linux-kernel - Centos 6.3 (2.6.33) hwclock not defaulting to --directisa mode on select() timeout util-linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CA+ekxPWi=rKffVBaB_Y-ro5vhMHGHboWVad6KRYt0Xd-7_o8MA@mail.gmail.com>
Date:	Sun, 21 Apr 2013 13:09:08 -0600
From:	Jeffrey Merkey <jeffmerkey@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Centos 6.3 (2.6.33) hwclock not defaulting to --directisa mode on
 select() timeout util-linux

On the older P4 systems from HP, the util-linux hwclock is no longer
defaulting to --directisa port setting mode if the select() timeout
fails.  It only shows up when you have an old PC with a battery that's
screwed up on the motherboard and the clock doesn't stay up to date.
But whether this is the case or not, ntpdate and ntpd should still be
able to update the system time and resync the hwclock.  I fixed it by
adding --directisa to the /etc/rc.d/rc.sysinit script but the
util-linux should default anyway if there is a failure as a failsafe
mode.

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/