SCIENTIFIC-LINUX-USERS Archives

March 2007

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Troy Dawson <[log in to unmask]>
Reply To:
Troy Dawson <[log in to unmask]>
Date:
Fri, 9 Mar 2007 13:57:02 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (108 lines)
Hi Denice,

Since updating java sometimes causes problems, we're leaving it up to 
the admins to do it by hand if they need to.  Here are the instructions.

SLF3
yum -c ftp://linux.fnal.gov/linux/lts30rolling/testing/yum.conf update

SLF4
yum -c ftp://linux.fnal.gov/linux/lts4rolling/testing/yum.conf update
or
yum --enablerepo=fermi-testing update

I think a majority of people do not want me pushing out rpm's that could 
potentially remove their hand installed java, on a friday evening.

I'm sorry, but I found out about the java problem too late to get a 
proper solution that wasn't going to cause more problems than it solved.

Troy

Denice wrote:
> On Fri, 9 Mar 2007, Troy Dawson wrote:
> 
> {snip}
>>
>> But have you actually tested to see if the change was really needed. 
>> Doing a diff and other various things aren't really telling you if 
>> something was broken in the first place.  I was given another java 
>> script, that works for all places I believe.
> 
>> ------
>>   import java.util.Date;
>>
>>    public class TimeCheck {
>>      public static void main(String[] arg) {
>>     System.out.println(new Date(1173599999999L).toString());
>>     System.out.println(new Date(1173600000000L).toString());
>>     System.out.println(new Date(1194159599999L).toString());
>>     System.out.println(new Date(1194159600000L).toString());
>>      }
>>    }
>> ------
>>
>> So, for your case, you would complie this code and then run
>>
>> /usr/java/j2sdk1.4.2_12/bin/java TimeCheck
>>  and then
>> /usr/java/j2sdk1.4.2_12.sv/bin/java TimeCheck
>>
>> And see if they are the same or different.
> 
> well:
> 
> $ cat /etc/sysconfig/clock ZONE="America/Vancouver"
> UTC=true
> ARC=false
> 
> # rpm -e j2sdk
> # rpm -ivh j2sdk-1.4.2_12-fcs.i586.rpm $ export 
> PATH=/usr/java/j2sdk1.4.2_12/bin:$PATH
> $ javac DSTCheck.java $ java DSTCheck
> Hello, you are running Sun Microsystems Inc. JVM version: 1.4.2_12
> 
> OLD Daylight Saving Time (DST) dates: Apr 1 - Oct 28
> NEW DST dates: Mar 11 - Nov 4
> Now (2007-03-09 11:41:16 PST) DST offset: 0 hours
> 2007-03-12 01:00:00 PST DST Offset: 0 hours
> 2007-04-02 01:00:00 PDT DST Offset: 1 hours
> 2007-10-27 01:00:00 PDT DST Offset: 1 hours
> 2007-11-03 01:00:00 PST DST Offset: 0 hours
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> ! YOUR JVM REQUIRES UPDATES FOR NEW DST CHANGES !
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> 
> # rpm -Fvh ~deatrich/j2sdk-1.4.2_13-fcs.i586.rpm
> $ export PATH=/usr/java/j2sdk1.4.2_13/bin:$PATH
> $ rm DSTCheck.class $ javac DSTCheck.java $ java DSTCheck
> Hello, you are running Sun Microsystems Inc. JVM version: 1.4.2_13
> 
> OLD Daylight Saving Time (DST) dates: Apr 1 - Oct 28
> NEW DST dates: Mar 11 - Nov 4
> Now (2007-03-09 11:43:24 PST) DST offset: 0 hours
> 2007-03-12 01:00:00 PDT DST Offset: 1 hours
> 2007-04-02 01:00:00 PDT DST Offset: 1 hours
> 2007-10-27 01:00:00 PDT DST Offset: 1 hours
> 2007-11-03 01:00:00 PDT DST Offset: 1 hours
> ...............
> . Your JVM is OK with the new DST changes .
> ...............
> 
> The regional timezone issue really is the bottom line..
> 
>  cheers,
>   denice
> -- 
> deatrich @ triumf.ca, Science/Atlas         PH: +1 604-222-7665
> <*> This moment's fortune cookie:
>     "Quando omni flunkus moritati"
>         - Red Green


-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI DSS Group
__________________________________________________

ATOM RSS1 RSS2