On 7/14/06, Stephen Gran <[EMAIL PROTECTED]> wrote:
On Fri, Jul 14, 2006 at 12:27:13PM -0700, J. Chieppa said: > Stephen, > > Here's the output I'm looking: > > relay-01:/etc# host -t txt current.cvd.clamav.net > current.cvd.clamav.net text "0.88.3:39:1599:1152901741:1" > relay-01:/etc# perl -e 'printf "%d\n", time;' > 1152915750 > > 3 * 3660 = 10980 and the difference I'm seeing here is 14009. What's really > strange is that both the server that's having the issue and the server that > is working fine are using the exact same DNS server. I mistyped slightly (3660 instead of 3600) but I think you get my point. Run the test on each server - do both show the same time? Do both show the same txt record? Does the one malfunctioning have a caching name server? This is the line of reasoning to follow. Either one of them has a bad clock, or one one of them has a bad cache. Take care, -- -------------------------------------------------------------------------- | Stephen Gran | Your wig steers the gig. -- Lord | | [EMAIL PROTECTED] | Buckley | | http://www.lobefin.net/~steve | | --------------------------------------------------------------------------
Stephen, Thanks for pointing me in the right direction (timestamps). The problem was actually caused by the system clock on the new server being 3 hours ahead even though I could have sworn I installed a NTP service. Once I got that sorted out, freshclam behaves like it should. Thanks, Jesse _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
