Red Hat Bugzilla – Bug 132385
/etc/localtime is configured too late during install
Last modified: 2007-11-30 17:10:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
bind-chroot copies /etc/localtime to /var/named/chroot/etc/localtime.
Oddly, even though I select America/Sao_Paulo as the timezone early
in the install, the file copied by bind-chroot's %post script is the
America/New_York localtime file. The timestamp of /etc/localtime
shows it was only set up for the timezone I selected at the end of the
install. This means that any chroot packages that copy /etc/localtime
will get it wrong. Would it be possible to get anaconda (or glibc?)
to install this file with the selected timezone earlier?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Select a timezone other than America/New_York in the installer
2.Perform a full everything install (or at least something that
3.After the install is complete, compare /etc/localtime with
Actual Results: They're different. The latter is America/New_York,
while the former is whatever you selected.
Expected Results: They're supposed to be the same.
This is related with bug 106572.
It would be great if we could make /var/named/chroot/etc/localtime
a link to /etc/localtime; but if it is a symbolic link, it will not
work during chroot, and if it is a hard link, this will not work if
/var is on a separate partition to / .
I can change the named initscript to check if /etc/localtime is
identical to /var/named/chroot/etc/localtime and copy it again
if not; that might be simpler than fixing it in anaconda.
I can't write /etc/localtime earlier because the source file doesn't
exist until after packages are put on the system. The packaging needs
to be fixed.
I'll fix this in BIND as described in comment #1 above.
*** This bug has been marked as a duplicate of 106572 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.