Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 4802 - Glibc upgrade mangles /etc/localtime dereferencing
Glibc upgrade mangles /etc/localtime dereferencing
Product: Red Hat Raw Hide
Classification: Retired
Component: glibc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-08-31 09:35 EDT by Pekka Savola
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-08-31 15:58:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pekka Savola 1999-08-31 09:35:35 EDT
It seems Glibc upgrade de-referenced my /etc/localtime
symbolic links (from /usr/share/zoneinfo/Europe/Helsinki)
pretty badly:

-- `date` --
Tue Aug 31 13:30:51 /etc/localtime 1999

Copying the correct zoneinfo file by hand and renaming it
to localtime seemed to work fine:

-- `date`  --
Tue Aug 31 16:31:55 EEST 1999
Comment 1 Bill Nottingham 1999-08-31 13:51:59 EDT
Do you know when this was done? glibc's script doesn't dereference
the symlink ; that's done in timeconfig/initscripts.
The %post seems to work OK currently.
Comment 2 Pekka Savola 1999-08-31 15:01:59 EDT
I'm not 100% sure, but I think the update before the last (w/ autorpm)
from ftp.sunet.se mirror was conducted at:
Fri Aug 20 12:37:27 (GMT+2)

And the last either
Tue Aug 24 12:24:26 or
Wed Aug 25 00:11:09

I couldn't reproduce this playing w/ glibc, timeconfig or initscripts.

Comment 3 Bill Nottingham 1999-08-31 15:58:59 EDT

I think that at some point the %post was broken in
initscripts/timeconfig, but it's since been fixed. However,
you might have upgraded during the broken time.

In the meantime, I'll mark this as fixed for the next release.

Note You need to log in before you can comment on or make changes to this bug.