After installing RH linux 6.x (and also RH 5.x) there is a problem when you
run "linuxconf". Linuxconf reports several faults in configuration files in
the form of: "httpd.conf has a revision date in the future, system time may
be wrong at some time".
RH5.x needed about 8hours to "selfcorrect the problem". RH6.x seems to work
fine after 2 hours. Probably at install time, there are some configuration
files written to disk with the wrong time-offset.
At install time I use timezone "Europe/Brussels".
hardware clock set to GMT off
If I use RH6.2 text-install and I toggle "Hardware clock set to GMT"
several times (and then I put it off again), the problem doesn't occur.
Doing thesame in the graphic install or the text installs of other RH 6.x,
the problem stays.
It is not really big problem...linuxconf is able to save all configuration
data perfectly, but it's rather annoying when it display's 10 warnings
about different configuration files.
This is a known bug that will be resolved in the next release of the operating
verified ... some time zone selections cause the post install reboot to have a
date different from the installed time ...
for example, selecting Europe/London w/no GMT: reboot is -1 hours from install
*** Bug 12229 has been marked as a duplicate of this bug. ***
After the installation (Czech, timezone Europe/Prague, +0100) are the files modified in the future (2 hours, it look like Moscow time or something like
/etc/fstab, /etc/modules.conf, ....
*** Bug 20049 has been marked as a duplicate of this bug. ***
Experienced this with Florence beta2.
Timezone Europe/Ljubljana ( GMT+2 )
Many files ( all the /* directories )have times in future.
It is the same in Fisher.
This is very likely related to bug 12155
Deferring until a future release.
Has anyone seen this problem with Red Hat Linux 7.2 or the recent Skipjack beta?
Closing due to inactivity - please reopen if you have additional comments to add
to this bug.
Still present in RHL 8.0
Same in beta 8.0.90. System complain about /etc/mail/* files modified in the
future (as init script uses command make).
Too bad, too old bug :-(
*** This bug has been marked as a duplicate of 6175 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.