On Fri, 16 Jan 2015, King Beowulf wrote: > This 1st thing I would check is the BIOS clock. Sometimes the OS can't > set it correctly if it's too far off. The BIOS click can get jiggered from > power outages of similar power glitches. > > Then check your time zone > Then check/set date
Ed, Essentially did these checks. Then I stepped back a bit and recalled that the hardware clock is used to keep time only when the system is shut down. As this server/workstaion is up 24/7/365(6) and ntpd is running, it uses system time and hwclock really does not matter. But, that information might well be out of date. > Note that ntpd will refuse to set the time if the current time is too far > off. Yep. > Next check the ntp time server adresses. Not all are allowed for the > general public. I'm using the ones in the Slackware-14.1 /etc/ntp.conf: # NTP server (list one or more) to synchronize with: server 0.pool.ntp.org iburst server 1.pool.ntp.org iburst server 2.pool.ntp.org iburst server 3.pool.ntp.org iburst > I'm at Denver airport so I'll check when I get in which time servers I'm > using. Hope it's for a skiing vacation rather than work. :-) Travel easy, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
