After installing rhl 7.2.90 and booting it, some system files have time in future. There is a symptom right at boot : Starting lpd: No Printers Defined [ OK ] Starting sendmail: make: *** Warning: File `virtusertable.db' has modification time in the future (2002-02-20 23:37:17 > 2002-02-20 22:57:32) make: warning: Clock skew detected. Your build may be incomplete. [ OK ]
Is this for Hampton Beta 1?
This is happening because we don't set the timezone during the installer (dupe of another bug assigned to msw iirc)
Yes, this is for Hampton Beta 1 ( and all previous RHL versions, for that matter ). As I see it, this is what happens : -installer CD boots. -CMOS clock is read and interpreted as if it were in UTC. -files are installed -the new installation is booted -time from the CMOS clock is read, this time correctly So if UTC time is 10:00 and my timezone is GMT-1 ( Europe/Ljubljana ), so my localtime is 11:00, which is also in the CMOS clock, then the installer sets the system time to 11:00 UTC, which is wrong and in the future, while the installed system , when booted after installation,when CMOS is 11:20 ( assume installation took 20 minutes ) , correctly sets the system time to 10:20 UTC ( and then complains that some files have time set to 11:00 UTC ) Recommended fix : after the user selects his timezime and is_CMOS_UTC settings, run hwclock again, with the correct parameters and environment.
*** Bug 60428 has been marked as a duplicate of this bug. ***
No surprise: the bug is still present in Hampton beta2
Deferring to future release.
Bug properly "deffered" to RHL 8.0. ( bug still present )
*** This bug has been marked as a duplicate of 6175 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.