From owner-freebsd-current Thu Dec 16 0:49:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 17EF715516 for ; Thu, 16 Dec 1999 00:49:30 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA14781; Thu, 16 Dec 1999 09:49:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kevin Day Cc: 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: Your message of "Thu, 16 Dec 1999 01:58:52 CST." <199912160758.BAA87332@celery.dragondata.com> Date: Thu, 16 Dec 1999 09:49:07 +0100 Message-ID: <14779.945334147@critter.freebsd.dk> From: Poul-Henning Kamp 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. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message