> : If people do a "settimeofday" we change the boot time since the > : amount of time we've been up *IS* known for sure, whereas the boottime > : is only an estimate. > > There is one problem with this. The amount of uptime isn't the same > as the amount of time since the machine booted. How can this happen? > When a laptop suspends, it doesn't update the update while it is > asleep, nor does it update the uptime by the amount of time that has > been slept. FWIW, we had code in the tree (just before the timeout_ch changes) that did update all of the timeouts to 'fire' when the laptop was resumed. This caused a 'thundering herd' problem at resume, but I don't see any way around it... However, it was lost when we changed to the different timeout code. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: Serious server-side NF... Poul-Henning Kamp
- Re: Serious server-side NF... Warner Losh
- Re: Serious server-side NF... Poul-Henning Kamp
- Re: Serious server-side NF... Warner Losh
- Re: Serious server-side NF... Tom Bartol
- Re: Serious server-side NF... Warner Losh
- Re: Serious server-side NF... Tom Bartol
- Re: Serious server-side NF... Warner Losh
- Re: Serious server-side NF... Tom Bartol
- Re: Serious server-side NF... Mike Smith
- Re: Serious server-side NF... Nate Williams
- Re: Serious server-side NF... Andrew Kenneth Milton
- Re: Serious server-side NF... Kevin Day
- Re: Serious server-side NF... Poul-Henning Kamp
- Re: Serious server-side NF... Matthew Dillon
- Re: Serious server-side NFS problem Andrew Gallatin
- Re: Serious server-side NFS problem Doug Rabson
- Re: Serious server-side NFS problem Matthew Reimer
- Re: Serious server-side NFS problem Mike Smith
- Re: Serious server-side NFS problem Matthew Dillon