John DeDourek ([EMAIL PROTECTED]) said:
> What we see in the /var/log/messages file is that after a reboot
> ("shutdown -r now"), the booting messages are correctly time stamped
> from
> the first apparent bootup message ("syslogd 1.1-3: restart") through the
> cron start message ("crond: crond startup succeeded"). The next message
> ("rc.sysinit: Loading default keymap succeeded") has the wrong time, 4
> hours late (our offset from UTC). This continues through "rc.sysinit:
> Checking filesystems succeeded". The next message "Mounting local
> filesystems succeeded" resumes the proper time stamping.
What you're seeing here is actually messages from earlier in the
boot ineterleaved with later messages (since they aren't passed
to syslog until after syslog is started.) The timestamp on these
is whatever time the system thought it was when the message
was generated; if the message is from when before the clock
is set, it might not have the 'correct' time.
This is why in 6.1 we try and set the clock as soon as possible
after booting...
Bill
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
