Warning: time of day goes back, taking countermeasures.(?)
warquel at hotmail.com
Sun Nov 4 20:13:54 PST 2001
It's nothing to worry about. As a matter of fact, you'll notice that this
happens when you run ping on localhost. I can't remember what the problem is
but it has something to do with a small bug in the kernel dealing with
timestamp comparisions. I have all my systems syncing with a time server
daily and still run into the problem. You can make this message disappear by
using '-U' in your ping command. This will disable some of the newer
features of ping in the newer kernel which, in turn, automagically fixes the
ping -U 10.0.0.23
Warren Raquel MCP CCNA
- Just another geek.
>From: "Jake" <Jake at callatg.com>
>Reply-To: <talk at nblug.org>
>To: "00 nblugTalk" <talk at nblug.org>
>Subject: Warning: time of day goes back, taking countermeasures.(?)
>Date: Sun, 4 Nov 2001 19:48:38 -0800
>Any ideas on what this means?
>[error at invictus error]$ ping 10.0.0.23
>PING 10.0.0.23 (10.0.0.23) from 10.0.0.1 : 56(84) bytes of data.
>Warning: time of day goes back, taking countermeasures.
>64 bytes from 10.0.0.23: icmp_seq=0 ttl=255 time=3.069 msec
>64 bytes from 10.0.0.23: icmp_seq=1 ttl=255 time=2.261 msec
>--- 10.0.0.23 ping statistics ---
>2 packets transmitted, 2 packets received, 0% packet loss
>round-trip min/avg/max/mdev = 2.261/2.665/3.069/0.404 ms
>Why does the time of day go back? What countermeasures is it taking?
>It seems strange...
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
More information about the talk