Woof! On Wed, 03 Sep 2008 10:26:55 -0400, Damian Krzeminski <[EMAIL PROTECTED]> wrote: > I think it can happen when JVM has a different opinion on if you are in > DST > or not ;-) > It's usually not just sipXconfig but any Java application that is > affected. > I wrote a small tester once (attached). > Try this: > > java Time > > And compare the output to /etc/sysconfig/clock and date output.
Very odd. With /etc/localtime pointing to /usr/share/zoneinfo/America/Los_Angeles: $ date -u; date; java Time Wed Sep 3 17:44:10 UTC 2008 Wed Sep 3 10:44:10 PDT 2008 September 3, 2008 9:44:10 AM GMT-08:00 Time zone:GMT-08:00 GMT-08:00 In DST:false Uses DST:false DST offset:0 With /etc/localtime pointing to /usr/share/zoneinfo/America/New_York: date -u; date; java Time Wed Sep 3 17:45:06 UTC 2008 Wed Sep 3 13:45:06 EDT 2008 September 3, 2008 12:45:06 PM GMT-05:00 Time zone:GMT-05:00 GMT-05:00 In DST:false Uses DST:false DST offset:0 So java "knows" about the GMT offset, but not daylight savings. With TZ set: TZ="America/New_York" java Time September 3, 2008 1:46:29 PM EDT Time zone:Eastern Standard Time America/New_York In DST:true Uses DST:true DST offset:3600000 It knows about both. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
