On Tuesday 28 July 2009 18:42:05 Russ Cox wrote: > On Tue, Jul 28, 2009 at 3:16 PM, erik quanstrom<quans...@quanstro.net> wrote: > > ignoring little bugs is the path to ruin. > > That's why the print should just go away entirely. > The code assumes that the time from one boot > to the next only ever increases, which has been > demonstrated not to be true. Maybe during one > boot your clock is screwed up for one reason or > another and you don't notice for a few days. > Then when you fix it, venti prints messages ad > infinitum? That's just broken behavior. > > It's not a question of time zones. Time zones don't matter. > It's just that the clock was wrong before and later is > correct--there are many reasons this might happen-- > and venti shouldn't care. > > The time stamps, like the ones in a file system, are > informational. It's okay if they're wrong. There's no > need to print. >
The problem isn't confined to unnecessary warning messages being printed. What about the 'arena arenas00: header is out-of-date' error, and the subsequent re-indexing (on every reboot) which occurs as a result of the condition? I'm new here... so I don't know... What I do know is that I'm having real and present issues with venti, that are in some direct or indirect way related to at least one or more of the following actors: bios/rtc clock /env/timezone /dev/rtc aux/timesync
