Hi, > > Jason Pyeron sent a missive on 2010-08-12: > > > > > We have a local time server and all of our machines are > > pointed at it > > > for the time. > > > > > > How can the clock drift by a day and a half? > > > > > > [root at devserver21 ~]# date > > > Fri Aug 13 14:43:29 EDT 2010 > > > [root at devserver21 ~]# rdate -s 192.168.1.67 > > > [root at devserver21 ~]# date > > > Thu Aug 12 07:02:39 EDT 2010 > > > [root at devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ > > > restrict default nomodify notrap noquery restrict 127.0.0.1 server > > > 192.168.1.67 server 192.168.1.66 server 192.168.1.65 > > > server 127.127.1.0 # local clock > > > fudge 127.127.1.0 stratum 10 > > > driftfile /var/lib/ntp/drift > > > broadcastdelay 0.008 > > > keys /etc/ntp/keys > > > > > > > > > > Hi, > > > > It is unlikely that the machine in question drifted forward > > in time if ntpd was running. Have a look at the logs > > /var/log/messages it should contain the ntpd log messages > > [root at devserver21 ~]# grep ntpd /var/log/messages > </snip> /SNIP > Jul 29 17:47:24 devserver21 ntpd[3475]: synchronized to LOCAL(0), > stratum 10 > Aug 12 22:48:29 devserver21 ntpd[3475]: sendto(192.168.1.66): Operation > not > permitted > [root at devserver21 ~]# uptime > 08:10:19 up 164 days, 9:56, 2 users, load average: 0.20, 0.54, 0.81 > [root at devserver21 ~]# What happened between July 29 and now? Is there nothing in the logs for that period? Rgds S.