Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DST change in 2007 on RHEL 2

Status
Not open for further replies.

murali2104

Technical User
Jul 6, 2005
43
IN
Hi,
I am looking ta the patches for US DST changes for year 2007. But did not get any thing working.

can you please help me?

one more, where to set TZ on a RHEL box (I wonder if there is any file like /etc/default/init for solaris where we maintain teh TZ info, and modify as we wish)
 
I am not sure how I can add new TZ entries in to my system.
any rpms/patches????

I do not want teh POSIX notation.
 
You didn't read the thread, did you? You just scanned it, right.

Hint: my post in that thread mentions the name of a package on FC6 that contains the timezone data.



Want the best answers? Ask the best questions! TANSTAAFL!
 
Thank You. But still I am not clear.
# find / -name '*tzdata*' -print
/usr/src/redhat/SPECS/tzdata.spec
/usr/src/redhat/SOURCES/tzdata-2006m-wa.patch
/usr/src/redhat/SOURCES/tzdata-2006m-brazil.patch
/usr/src/redhat/SOURCES/tzdata-base-0.tar.bz2
/usr/src/redhat/SOURCES/tzdata2006m.tar.gz

where shall I mention? or shall I just
"export TZ=CST6CDT"?

# zdump -v CST6CDT | grep 2007

CST6CDT Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 gmt
off=-21600
CST6CDT Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 gmt
off=-18000
CST6CDT Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 gmt
off=-18000
CST6CDT Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0 gmt
off=-21600
 
You're set. The DST change will occur on Mar 11 instead of the first Sunday in April, so you have the current timezone file.

On my RHEL4 system, the current package is tzdata-2006m-3.el4.
 
I don't understand what you're asking.

The output of your zdump matches exactly the dates from mine. And since you read the thread completely, you already know whether I do or do not think March 11 and November 4 are the correct new dates for changing. Even if you hadn't read the thread completely, you might have issued the command:

zdump -v CST6CDT | grep 200[red]6[/red]

and checked what the dates were for 2006. If the dates for 2007 were a couple of weeks earlier in the spring and a couple of weeks later in the fall, you might have compfortably assumed that your server's clocks would change when you needed them to.




Want the best answers? Ask the best questions! TANSTAAFL!
 
Just found this thread to get me started; thanks guys.

Current timezone is defined in /etc/sysconfig/clock
zdump reads compiled file in /usr/share/zoneinfo, e.g.
$ zdump -v America/Vancouver |grep 2007
(but it doesn't error if there's no such zone)

zoneinfo file is created from rules by zic
On RedHat, this is in SRPMS and installs as e.g.
/usr/src/redhat/BUILD/tzdata/tzdata2006a/northamerica
(lots of notes and historical detail)

On Fedora Core, it's in the tzdata package.
On RedHat 7-9, it's in glibc-common
On Mandriva and Mandrake, it's in timezone
FC4 and newer, RHEL have updates available (but you have
to do them e.g. "yum update tzdata")
FC1, RH9 were on Fedora-legacy updates, which stopped.

So it looks like we need to back-port the current rules
for northamerica and compile it, then make an RPM for
easier management, to update older machines. We
have about 100 needing updates cf. 130 already OK.

One rules file I looked at on FC1 had the updates for
the US but not for Canada, as the legislation had not
been passed at that point.

Y2K all over again, in miniature. Windows NT4 and earlier
won't be updated automatically, either. And DST still
won't change on the same dates as Europe.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top