Does anyone know if/where the patch is the DST time change that is coming in March.
I see they had for solaris 7, but I have been searching and can not find anything that is for solaris 6.

 

 

This is just a guess on my part, and others will surely have more knowledge
on the subject, but I don't think the DST issue is going to be addressed for that OS.
At all.

Solaris 7 is still in Phase 2 of EOL support.
However Solaris 2.6 and older releases are already passed beyond that.
http://www.sun.com/service/eosl/solaris/solaris_vintage_eol_5.2005.xml
EOSL (End Of Service Life) has expired for 2.6

Glance at the PDF document that was specifically published for 2.6's EOL announcement:
http://www.sun.com/service/eosl/solaris/EOSL_Pre_Announcement.pdf

 

 

I was thinking that was the case. I just need to know if there is a work-around for this.

 

 

Unless there is some special application that requires timestamps
to include a reference to Daylight time versus Standard time,
then just have the system synchronize its system time to a public NTP server.

Here's a possible list. Pick one:
http://ntp.isc.org/bin/view/Servers/StratumTwoTimeServers

 

 

Amy Wright at Sun sent me the following regarding the DST patch for 2.6:

_____Begin copied text

Hello,

The Solaris 2.5.1, 2.6, & 7 DST patches can be purchased via T&M.

Below is some general information regarding the options for the DST
Patches. For more detailed information, please contact your account
management team.

Solaris 2.5.1, 2.6, & 7 DST Patches:

Due to a change in the Energy Policy Act of 2005, beginning in 2007,
Daylight Saving Time is extended one month and begins for most of the
United States at: 2 a.m. on the Second Sunday in March to 2 a.m. on the
First Sunday of November. As a result, Solaris Patches have been created
for Solaris 8, 9, & 10 to update your system and are available though
SunSolve. Vintage Solaris patches will be created for a fee for Solaris
2.5.1, 2.6, & 7.

These Vintage Solaris patches may be purchased via the normal Time and
Materials process. The part number to book the patches is TM-DST. The
cost is:

$10,000 per server (up to 15 servers)
$150,000 (greater than 15 servers)

You will receive all of the Vintage Solaris (2.5.1, 2.6 & 7) patches and may be
deployed only on the systems you have purchased these for. The patches are not to be
resold or distributed to customers. The patches will be available the second week of January 2007.

If you do not wish to purchase the Vintage Solaris DST Patches for a
fee, please consider migrating your system to a supported Solaris OS.

Please see the below URLs for more information on the policy changes.

BigAdmin:
http://bigadmin.eng.sun.com/bigadmin/features/techtips/dst_changes.html

Sun Alert:
http://sunsolve2.central.sun.com/search/document.do?assetkey=1-26-102178
-1&searchclause=102178
<http://sunsolve2.central.sun.com/search/document.do?assetkey=1-26-10217
8-1&searchclause=102178>

Daylight Saving Time, Its History and Why We Use It:
http://www.energy.ca.gov/daylightsaving.html

Energy Policy Act of 2005:
http://energycommerce.house.gov/108/energy_pdfs_2.htm

Best regards,
Amy
<http://www.sun.com> Amy Wright
Product Manager, Services

Sun Microsystems, Inc.
500 Eldorado Boulevard, UBRM03-304
Broomfield, CO 80021 US
Phone x74813/303.272.4813
Fax 303.272.8979
Email Amy.Wright@Sun.COM
____________________________End copied text

 

 

OUCHHHHHHHH! This pricing is going to leave a mark!

 

 

You Can manually change the timezone by just
editing some few files and reboot the server.
This is not the recommended approach.

 

 

Many folks have mentioned that the timezone files are binary compatible across Solaris versions (and even work on old SunOS 4.x installations).

I would save a copy of the /usr/share/lib/zoneinfo stuff and just copy over what you have from an older OS that has been patched. Then see if that works.

That won't take care of Java or libC issues, but it should handle the majority of things.

--
Darren

 

 

If I change TZ to GMT will the LibC still be an issue?

 

 

If you never use a POSIX format timezone, then the libC update is likely not an issue.

The setting of the system default is not a guarantee.

--
Darren

 

 

Here's an update on the price of the DST patch for SunOS 2.6 from Sun Time & Materials (T&M):

After speaking with our account rep, we were able to get the patch for $400 (it's priced per system, but we have only one 2.6 server). I don't know if this was some special deal for us, or if the folks within Sun just came to their senses.

I called Sun, went to the T&M queue, and explained what I needed. They generated a quote, waited for a PO, and then responded with a link where I could download the patch.

hth,
Steve Adams
Ithaca College

 

 

Here's what I did :

wget ftp://elsie.nci.nih.gov/pub/tzdata2007c.tar.gz

 gzip -d -c tzdata2007c.tar.gz | tar xvf - 

From the file called northamerica replace all "00u" with "00"

zic -d `pwd`/zoneinfo northamerica

cd zoneinfo

(tar cf - *) | (cd /usr/share/lib/zoneinfo; tar xvf -)

Then edit /etc/default/init and Change:

TZ=US/Pacific

To:

TZ=America/Los_Angeles

and reboot.

 

 

Why would you do this? Does the 'zic' in 2.6 have a problem with those lines?


Any reason you don't just make all the files so everything is up to date?


Make all the files and this isn't necssary. The link between those names is in the 'backward' file.

--
Darren

 

 

I'm on 2.5, but yes zic fails - I get this message and many more like this:

"northamerica", line 125: invalid time of day

 > > zic -d `pwd`/zoneinfo northamerica

Nope - I'd have had to fix all the files. But make everything would be a more global solution.


Thanks. For people who do compile backward - make sure you compile it as the last file.

 

 

Does anyone know how to do this without a reboot? I have some critical servers where I did the procedure I recommended above. On the ones I could reboot - they're fine. the ones that I can't reboot still show the old timezone