From owner-freebsd-java@FreeBSD.ORG Tue Jun 28 22:51:29 2005 Return-Path: X-Original-To: freebsd-java@freebsd.org 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 E169B16A41C for ; Tue, 28 Jun 2005 22:51:29 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out3.tiscali.nl (smtp-out3.tiscali.nl [195.241.79.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79D3A43D4C for ; Tue, 28 Jun 2005 22:51:29 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from guido.klop.ws (unknown [82.171.39.195]) by smtp-out3.tiscali.nl (Postfix) with SMTP id BA6148013538 for ; Wed, 29 Jun 2005 00:51:28 +0200 (CEST) Received: (qmail 835 invoked from network); 28 Jun 2005 22:51:27 -0000 Received: from localhost (HELO outgoing.local) (127.0.0.1) by localhost with SMTP; 28 Jun 2005 22:51:27 -0000 Date: Wed, 29 Jun 2005 00:51:26 +0200 To: "Achilleus Mantzios" References: From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: User-Agent: Opera M2/8.01 (FreeBSD, build 1204) Cc: freebsd-java@freebsd.org Subject: Re: Wierd problem in linux 2.4.18-bf2.4, Java Blackdown-1.4.2-rc1 (Solved) 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, 28 Jun 2005 22:51:30 -0000 On Tue, 28 Jun 2005 08:25:12 +0200, Achilleus Mantzios wrote: > O Ronald Klop έγραψε στις Jun 27, 2005 : > >> On Mon, 27 Jun 2005 11:14:14 +0200, Achilleus Mantzios >> wrote: >> >> > >> > Forgot my homework.... >> > A classic (lack of) consumption of output situation, >> > >> >> From the java docs: >> > >> > The Runtime.exec methods may not work well for special processes on >> > certain native platforms, such as native windowing processes, daemon >> > processes, Win16/DOS processes on Microsoft Windows, or shell scripts. >> > The >> > created subprocess does not have its own terminal or console. All its >> > standard io (i.e. stdin, stdout, stderr) operations will be >> redirected to >> > the parent process through three streams (Process.getOutputStream(), >> > Process.getInputStream(), Process.getErrorStream()). The parent >> process >> > uses these streams to feed input to and get output from the >> subprocess. >> > Because some native platforms only provide limited buffer size for >> > standard input and output streams, failure to promptly write the input >> > stream or read the output stream of the subprocess may cause the >> > subprocess to block, and even deadlock. >> > >> > >> > Sorry for the noise, the situation can pretty well >> > occur in FreeBSD too when pipe output buffer reaches its limit, >> > and at the end of the day i think someone maybe will find this >> > useful in the future. >> >> I always create two threads to copy the output of stdout and stderr to >> some place. (/dev/null or a file or System.out). In java 5 you can >> combine >> stdout and stderr, so you only need 1 thread. >> > > Right, altho doing >> dev/null 2>&1 > in the script itself, saves the extra code. I know scripting. We were talking about Java. Coding in java expecting a script is doing something you like is not failsafe. -- Ronald Klop Amsterdam, The Netherlands