From owner-freebsd-java Sat Jan 31 12:26:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00454 for java-outgoing; Sat, 31 Jan 1998 12:26:27 -0800 (PST) (envelope-from owner-freebsd-java@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00449 for ; Sat, 31 Jan 1998 12:26:26 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA00776; Sat, 31 Jan 1998 13:26:24 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA21411; Sat, 31 Jan 1998 13:24:02 -0700 Date: Sat, 31 Jan 1998 13:24:02 -0700 Message-Id: <199801312024.NAA21411@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Craig Spannring Cc: freebsd-java@FreeBSD.ORG Subject: Re: Bug in java.lang.Process.waitFor()? In-Reply-To: <199801310308.TAA24210@bangkok.office.cdsnet.net> References: <199801310308.TAA24210@bangkok.office.cdsnet.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java" > I can't seem to get the waitFor() to ever return. The problem appears > in both jdk1.1.5 port and the jdk1.1.2 for FreeBSD. The waitFor() in > the Windows jdk1.1.4 seems to work fine the way I'm using it. For what it's worth, the fix to the waitFor() problem was quite simple and due to some code that Damon added. That code might be necessary for some other feature, but he has house guests and (apparently) hasn't been near his computer to answer email. However, after that was fixed, it revealed another problem we have with the FD reaper threads that are created when a process is instantiated, which causes the applet/application to never exit when it should unless you explicitly add a 'System.exit(0)' call at the end. I'm working on this, and hope to have a fix committed and a new JDK release rolled before the end of the weekend. Nate