Date: Thu, 16 Dec 1999 10:18:48 -0700 From: Nate Williams <nate@mt.sri.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Kevin Day <toasty@dragondata.com>, 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: <199912161718.KAA19547@mt.sri.com> In-Reply-To: <14779.945334147@critter.freebsd.dk> References: <199912160758.BAA87332@celery.dragondata.com> <14779.945334147@critter.freebsd.dk>
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. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912161718.KAA19547>