In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes: : 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. IS this a bug in the apm code? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: Serious server-side NFS problem Andrew Gallatin
- Re: Serious server-side NFS problem Mike Smith
- Re: Serious server-side NFS problem Garrett Wollman
- Re: Serious server-side NFS problem Matthew Dillon
- Re: Serious server-side NFS problem Mike Smith
- Re: Serious server-side NFS problem Rodney W. Grimes
- Re: Serious server-side NFS problem Poul-Henning Kamp
- Re: Serious server-side NFS problem Nate Williams
- Re: Serious server-side NFS problem Peter Wemm
- Re: Serious server-side NFS problem Poul-Henning Kamp
- Re: Serious server-side NFS problem Warner Losh
- Re: Serious server-side NFS problem Poul-Henning Kamp
- Re: Serious server-side NFS problem Warner Losh
- Re: Serious server-side NFS problem Tom Bartol
- Re: Serious server-side NFS problem Warner Losh
- Re: Serious server-side NFS problem Tom Bartol
- Re: Serious server-side NFS problem Warner Losh
- Re: Serious server-side NFS problem Tom Bartol
- Re: Serious server-side NFS problem Mike Smith
- Re: Serious server-side NFS problem Nate Williams
- Re: Serious server-side NFS problem Andrew Kenneth Milton