In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >Look at the snapshot below, taken right after boot time. Most entries are >at "Feb 5 22:34" which is boot time, but some other are "Feb 6 01:34" >which is in the future! It looks like TZ offset added for them by mistake. >Please fix this bug.
My guess: Your RTC has the wrong time and ntpdate or similar stepped your clock to be correct. There is nothing in DEVFS which knows about timezones, but there is code to set the initial time to the estimated boottime. If your system comes up, takes wrong time from RTC, the dev entries will get this wrong time before the system gets a chance to set it right across the network. Originally, the timestamps in DEVFS started out as zero, ie: 19700101000000 (moduls timezone) but people didn't like that and the abovementioned code was introduced. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
