Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Apr 2004 13:13:11 +0100
From:      Jez Hancock <jez.hancock@munk.nu>
To:        hugle <hugle@vkt.lt>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: microuptime() went backwards
Message-ID:  <20040423121311.GB41702@munk.nu>
In-Reply-To: <159171051438.20040423090456@vkt.lt>
References:  <159171051438.20040423090456@vkt.lt>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 23, 2004 at 09:04:56AM +0300, hugle wrote:

> SOmetimes I see such messages in dmesg.
> 
> perl# dmesg
> uptime() went backwards (1574174.333073 -> 1573478.944788)
> 
> what they mean? and what causes them to appear ?
> is it good or bad?? :)

I'd always presumed these messages occured on my machine because the
ntpd (network time protocol daemon) had adjusted the system clock.  I
can't actually tell you for sure since the messages aren't logged by
syslog here so there's no easy way of comparing the times to see if they
correspond to the ntpd adjustments.  

Check to see if you have ntpd running - if so that's probably the reason
for the messages.

-- 
Jez Hancock
 - System Administrator / PHP Developer

http://munk.nu/
http://jez.hancock-family.com/  - Another FreeBSD Diary
http://ipfwstats.sf.net/        - ipfw peruser traffic logging



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040423121311.GB41702>