From owner-freebsd-java@FreeBSD.ORG Tue Jun 8 09:42:21 2010 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D2361065678 for ; Tue, 8 Jun 2010 09:42:21 +0000 (UTC) (envelope-from michael.osipov@siemens.com) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mx1.freebsd.org (Postfix) with ESMTP id BD22C8FC15 for ; Tue, 8 Jun 2010 09:42:20 +0000 (UTC) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o589gJc5019743 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Jun 2010 11:42:19 +0200 Received: from DEMCHP99ET2MSX.ww902.siemens.net ([139.25.131.241]) by mail2.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o589gJCQ023628; Tue, 8 Jun 2010 11:42:19 +0200 Received: from DEMCHP99E24MSX.ww902.siemens.net ([169.254.1.144]) by DEMCHP99ET2MSX.ww902.siemens.net ([139.25.131.241]) with mapi; Tue, 8 Jun 2010 11:42:19 +0200 From: "Osipov, Michael" To: Roger Marquis , "freebsd-java@freebsd.org" Date: Tue, 8 Jun 2010 11:42:16 +0200 Thread-Topic: Timezone behavior of Java Thread-Index: AcsDLoYEET+hOC5KRFOFFuFvZjZL0QDvY5Wg Message-ID: References: <20100602120016.5B4BE1065696@hub.freebsd.org> <20100603145407.28CAE2B2131@mx5.roble.com> In-Reply-To: <20100603145407.28CAE2B2131@mx5.roble.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: Timezone behavior of Java X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2010 09:42:21 -0000 Roger Marquis wrote: >> If it works with your system then it must be something with ours. I >> have absolutely no idea what the cause might be. Any pointers? >=20 > There was a bug some years ago that caused a similar symptom, but only > when /etc/localtime was a symlink instead of a regular file. Thanks for the information. My problem has got resolved due to Mike's tip.=