Bug 5234 - need backward compatibility time zone config
need backward compatibility time zone config
Product: Red Hat Raw Hide
Classification: Retired
Component: timeconfig (Show other bugs)
i386 Linux
high Severity low
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
: 5395 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 1999-09-19 23:04 EDT by Ben Liblit
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-09-24 22:40:14 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 Ben Liblit 1999-09-19 23:04:32 EDT
When a program is running using the backward compatibility
libraries from "compat-glibc-5.2-", it will not have
proper time zone configuration.

This is most apparent when sending e-mail from Netscape
Communicator using the "netscape-communicator-4.61-9"
package.  The "Date:" header in outgoing mail incorrectly
gives UTC time zone "+000" rather than whatever the local
machine is actually configured to use.

(Note, however, that this is really not a Netscape bug.  It
is a time configuration bug that affects any date-sensitive
application using the backward compatibility libraries.
Netscape just happens to be the most prominent such

Perhaps we need a "compat-timeconfig" package to go along
with "compat-glibc" ?
Comment 1 Bill Nottingham 1999-09-24 22:40:59 EDT
Set TZ=:/etc/localtime.

This is fixed in the latest netscape packages (4.61-12.)
Comment 2 Bill Nottingham 1999-09-27 13:05:59 EDT
*** Bug 5395 has been marked as a duplicate of this bug. ***

Netscape does not set the right time zone for outgoing
emails unless the TZ environment variable is set, i.e.:

export TZ=:/etc/localtime

This could also be put in /etc/bashrc (and cshrc or
whatever), so that other apps will have access to TZ as

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