Home.... | log in.... | Pub my question! | Sign-up....

Java-index >> General >> Sys Admin Best Practices

timezone change for america on solaris 2.6

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.

[201 byte] By [LHradowya] at [2007-11-26 15:18:12]

«« JTable selection with mouse drag problem
»» An XJC compilation error - Could not load class (..) for type cvsversion

# 1

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

rukbata at 2007-7-8 11:00:37 >

top of Java-index,General,Sys Admin Best Practices...

# 2

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

LHradowya at 2007-7-8 11:00:37 >

# 3

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

rukbata at 2007-7-8 11:00:37 >

# 4

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

Steve_Adamsa at 2007-7-8 11:00:37 >

# 5

OUCHHHHHHHH! This pricing is going to leave a mark!

Lee_McCreerya at 2007-7-8 11:00:37 >

# 6

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

olumytea at 2007-7-8 11:00:38 >

# 7

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

Darren_Dunhama at 2007-7-8 11:00:38 >

# 8

> That won't take care of Java or libC issues, but it> should handle the majority of things.If I change TZ to GMT will the LibC still be an issue?> > -- > Darren

vadud3a at 2007-7-8 11:00:38 >

# 9

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

Darren_Dunhama at 2007-7-8 11:00:38 >

# 10

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

Steve_Adamsa at 2007-7-8 11:00:38 >

# 11

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.

venksia at 2007-7-8 11:00:38 >

# 12

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

> with "00"

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

> zic -d `pwd`/zoneinfo northamerica

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

> 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

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

Darren

Darren_Dunhama at 2007-7-8 11:00:38 >

# 13

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

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

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

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

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

> > Then edit /etc/default/init and Change:

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

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

venksia at 2007-7-8 11:00:38 >

# 14

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

venksia at 2007-7-8 11:00:38 >

# 15

> 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

A process caches the data from the timezone files after it launches. So there's no way to inform a running process to go back and re-read the new files, true whether you're applying a Solaris patch, running 'zic', or just copying them from another host.

The reboot isn't magic, it just makes sure that all the processes die and are restarted.

If you've got a big Oracle database that you can't bring down, I don't know any way to update that process.

But things like 'cron' can be restarted and they'll get the benefit of the updates.

So even on the server that you didn't reboot, running 'date' should show the correct time. Is that true?

Darren

Darren_Dunhama at 2007-7-21 16:22:46 >

# 16

> The reboot isn't magic, it just makes sure that all

> the processes die and are restarted.

Agreed - no magic there.

> So even on the server that you didn't reboot, running

> 'date' should show the correct time. Is that true?

Unfortunately it doesn't. This is what matters to me - I want new processes to have the correct time - I understand that daemons running before might never sync - till the next meltdown :).I tried this a lot on two non-critical machine before I gave up and rebooted.

venksia at 2007-7-21 16:22:46 >

# 17

I'm not sure what 2.6 might be doing.

I've done this a lot on 7 and up and on several Linux distributions. They've all worked without a reboot as long as the file was replaced and I wasn't using a POSIX timezone. I haven't been able to find a 2.6 installation to test.

Darren

Darren_Dunhama at 2007-7-21 16:22:46 >

Java programming resources: FAQs, tutorials, compiler and browser download sites, documentation, books lists, IDEs, etc.

timezone change for america on solaris 2.6

General New Topic

General Hot Topic

General

All Classified