I regularly get "microuptime() went backwards" warnings on my desktop
box. The funny thing about them is that the reported timevals have the
same seconds part, but the microseconds part of the second timeval is
so large that it's wrapped around to a negative number (causing the
signed comparison to report that it went backwards). This suggests
that the current process has been running uninterrupted for several
seconds, which seems unlikely - or that the timecounter was adjusted
upwards while the process was running (could ntp cause that?)

Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to