Date: Thu, 16 Dec 1999 09:49:07 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Kevin Day <toasty@dragondata.com> Cc: dillon@apollo.backplane.com (Matthew Dillon), gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem Message-ID: <14779.945334147@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 16 Dec 1999 01:58:52 CST." <199912160758.BAA87332@celery.dragondata.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14779.945334147>