From owner-freebsd-java@FreeBSD.ORG Sun Apr 27 15:42:34 2003 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E66DC37B401 for ; Sun, 27 Apr 2003 15:42:34 -0700 (PDT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13B7343F93 for ; Sun, 27 Apr 2003 15:42:34 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.9/8.12.9) with ESMTP id h3RMgWWv009195; Sun, 27 Apr 2003 18:42:32 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sun, 27 Apr 2003 18:42:31 -0400 To: Tom Samplonius From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.28 cc: freebsd-java@freebsd.org Subject: Re: Java on FreeBSD 5.0 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Apr 2003 22:42:35 -0000 At 12:46 PM -0700 4/27/03, Tom Samplonius wrote: >On Thu, 24 Apr 2003, Garance A Drosihn wrote: > >... >> In 'ps', I do notice some processes of: >> /usr/local/linux-sun-jdk1.4.1/bin/java -version >> >> which seem to be just sitting there. I also notice a >... > > This sounds like the bug that occurs when running the linux >jdk as non-root (it hangs). Try as root. I was running it as root. It turned out that the problem hitting me was due to a recent change to src/sys/compat/linux/linux_signal.c in the freebsd-current branch. The change was made early last week. The first attempt to fix the problem was made on Friday, but that didn't quite fix it. If you check the freebsd-current mailing list, in the thread on "Re: Linux compat broken??" there is a suggested patch from Tor Egge which fixed the problem I was having. I expect that patch will be committed very soon. So, if anyone else runs into this problem (which is possible since daemonnews just announced patchset 3), then you can probably just wait a day or two and then rebuild your freebsd-current world... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu