From owner-freebsd-current Thu Dec 16 9:19:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 69B6914DC2 for ; Thu, 16 Dec 1999 09:19:08 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id KAA06289; Thu, 16 Dec 1999 10:18:50 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA19547; Thu, 16 Dec 1999 10:18:48 -0700 Date: Thu, 16 Dec 1999 10:18:48 -0700 Message-Id: <199912161718.KAA19547@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Kevin Day , dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <14779.945334147@critter.freebsd.dk> References: <199912160758.BAA87332@celery.dragondata.com> <14779.945334147@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199912160758.BAA87332@celery.dragondata.com>, Kevin Day writes: > > >Ack, I was using this very same thing for several devices in an isolated > >peer-to-peer network to decide who the 'master' was. (Whoever had been up > >longest knew more about the state of the network) Having this change could > >cause weirdness for me too... I assumed (without checking *thwap*) that > >boottime was a constant. > > > >Perhaps a 'real_boottime' or 'unadjusted_boottime' that gets copied after > >'boottime' gets initialized so that others can use it, not just NFS? :) > > no, I think that is a bad idea. In your case you want to use the > "uptime" which *is* a measure of how long the system has been > running. Uptime is also a constantly changing number. Forgive me for my ignorance, but why does bootime constantly change? I would have thought it would be a constant? I've got software that also uses this to determine when a new copy of it exists (although I do keep a local cache of the value in case my software crashes, since it can recover from a crash, but not a reboot). I would think that boottime would be constant, since you didn't keep booting at a different time... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message