From: Ted Kaczmarek <tedkaz@optonline.net>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: RE: Time quirk, UTC on Java 5
Date: Mon, 07 Nov 2005 13:18:49 -0500 [thread overview]
Message-ID: <1131387529.3407.11.camel@pluto.linsolutions.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E678@liverpoolst.ad.cl.cam.ac.uk>
On Sat, 2005-10-29 at 15:26 +0100, Ian Pratt wrote:
> > I have been testing java 5 on some apps and I always see utc
> > timezone for the logging when running these on a xen guest.
> > All the regular logging timestamps are fine, only the java
> > ones are showing up as UTC.
> > Same setup on a non xen kernel on the same box the timestamps
> > are fine.
>
> Truly bizzare. The only thing I can think of is if it tries to run
> /sbin/hwclock or access /dev/rtc directly. You could try strace'ing it.
>
> Ian
Finally got back to this :-)
xen_changeset : Sun Nov 6 13:50:33 2005 +0100 7628:270469d40f02
dom0 and domU are Centos 4.2 with java version "1.5.0_05" installed.
Test java code
import java.util.Date;
import java.util.TimeZone;
public class TimeTest {
public static void main(String args[]) {
long time = System.currentTimeMillis();
String millis = Long.toString(time);
Date date = new Date(time);
System.out.println("Current time in milliseconds = " + millis +
" => " + date.toString());
System.out.println("Current time zone: " +
TimeZone.getDefault().getID());
}
}
On dom0 returns EST which is local timezone.
On domU returns GMT.
I didn't see rtc or hwclock accesed or used in any of the strace output.
http://paste.ubuntulinux.nl/4185
Nice python script I stumbled across.
http://ubuntu.wordpress.com/2005/09/12/script-to-post-terminal-output-to-pastebin/
Regards,
Ted
next prev parent reply other threads:[~2005-11-07 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 14:26 Time quirk, UTC on Java 5 Ian Pratt
2005-11-07 18:18 ` Ted Kaczmarek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-29 12:31 Ted Kaczmarek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1131387529.3407.11.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.