Re: named dying on INSIST

From: mike (mike@coloradosurf.com)
Date: 03/28/01 

Date: Tue, 27 Mar 2001 15:50:50 -0700
From: mike <mike@coloradosurf.com>
To: Matt Piechota <piechota@argolis.org>

Matt,

Thanks for your reply,

>
> My machine does this constantly. Are you also getting "microuptime wnet
> backwards" messages on the consle/syslog?
Well, this machine is remote, I'll have to dig through /var/log/messages
(which mirrors /dev/console) but I don't think so.

> Near as I can tell, my
> motherboard has an wonky clock chip, which FreeBSD/BIND can't handle. Odd
> thing is it never had issues until the FreeBSD 4.x series, I can't
> remember my 3.x machine ever having this problem.
That figures, this is a 3.5 Stable machine (when probems are found to have
consistency, problems are often solved ;). This is the first time it's
happened (but it's only been up 8-9 months).

> There's a few PRs is
> the GNATS database concerning this. Hopefully your problem will be solved
> by one of the fixes mentioned. It didn't fix mine. (I have an Open PR on
> it). Search on "microuptime" will find most of them (some are closed
> already, so they won't automatically show up in the search).
I'll have to look into it. Thanks.

> > INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000);
>
> This is completely right. The microseconds value of the uptime should
> never be outside of that range. Unfortunately, all is not well my
> machine.
Doh!

mike

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message