From owner-freebsd-security Tue Mar 27 14:56:21 2001 Delivered-To: freebsd-security@freebsd.org Received: from coloradosurf.com (c1520339-a.lakwod1.co.home.com [24.179.159.58]) by hub.freebsd.org (Postfix) with ESMTP id 7376437B718 for ; Tue, 27 Mar 2001 14:56:18 -0800 (PST) (envelope-from mike@coloradosurf.com) Received: (from mike@localhost) by coloradosurf.com (8.9.3/8.9.3) id PAA15596; Tue, 27 Mar 2001 15:50:51 -0700 (MST) (envelope-from mike) Date: Tue, 27 Mar 2001 15:50:50 -0700 From: mike To: Matt Piechota Cc: security@freebsd.org Subject: Re: named dying on INSIST Message-ID: <20010327155050.A15517@coloradosurf.com> References: <3.0.6.32.20010327153414.00b132e0@officeonweb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3.0.6.32.20010327153414.00b132e0@officeonweb.net>; from piechota@argolis.org on Tue, Mar 27, 2001 at 03:34:14PM -0700 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.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