Problem with external process on Linux using Runtime.exec() andoutput, input and error streams.

I've encountered a problem in using Runtime.exec() and the outputStream and inputStreams with Java on Linux. Apologies in advance for the very long message, but I've done a lot of analysis on this to narrow the problem, make it reproducible, try it under varying environments, etc. This

JDK1.2pre2: Problem launching java GUI app from Runtime.exec()

With Blackdown JDK 1.1x I could launch another java program with a GUI from Runtime.exec. It just works, first time. Now in JDK 1.2 it is more complicated: The exec environment now requires a "DISPLAY=localhost:0" The machine (Red Hat 5.1, Red Hat 6.0) needs xhost +localhost Thi

Re: Efficiency/GC problem with Runtime.exec()?

>Thanks - I really hadn't considered the fact that the call to readLine() may be >creating a lot of throw-away objects, too. I just saw that my loop was creating >one String object per iteration, so I thought, "That's not too bad." :) :) been there... thought that too... then found out The Hard

Re: Efficiency/GC problem with Runtime.exec()?

Chris Abbey wrote: > ...running 117_v1a, native, with the -verbosegc option I see that a quick run > on my "toy" system produced 137598 objects and 8000423 bytes worth of trash! > ... I would highly recommend that you > write your own readln method taking a char[] or a StringBuffer if you > _have

Re: Efficiency/GC problem with Runtime.exec()?

At 03:58 PM 3/19/99 +0100, Robb Shecter wrote: >I've noticed weird behavior with JDK1.1.7a (Suse 6.0) that I didn't see >with JDK 1.1.6: When doing the most basic system exec, and then reading >in the stdin, Java frequently hiccups, for a good second or two, usually >when garbage is collected. 1

Efficiency/GC problem with Runtime.exec()?

Hi, I've noticed weird behavior with JDK1.1.7a (Suse 6.0) that I didn't see with JDK 1.1.6: When doing the most basic system exec, and then reading in the stdin, Java frequently hiccups, for a good second or two, usually when garbage is collected. I found this because I've written a port of GNU

Re: Runtime.exec ()

> From: Mark Hofmann <[EMAIL PROTECTED]> > Subject: Re: Runtime.exec () > > Hi, > > I tried the same thing some time ago. > The problem is, exec works, for example if you try exec("ls") you wont get > problems. However, running anything as a command that

Re: Runtime.exec ()

Thanks to all that sent me the key: exec doesn't redirect I've rewritten my test applet to run a shell script that does the redirection for me. It works just fine. Marius Marius Schamschula, optical physicist, mac, and network coordinator The Center for Applied Optical Sciences: http://www.c

Re: Runtime.exec ()

. Anybody knows why ??? Mark Marius Schamschula wrote: > Hi there, > > I am having trouble getting Runtime.exec () to do anything (yes I do send > the desired command as an argument...e.g. "/bin/ls /home/someusr/dir > > /home/someusr/test"). I've tested my code o

Re: Runtime.exec ()

>>>>> Marius Schamschula writes: Marius> Hi there, Marius> I am having trouble getting Runtime.exec () to do anything Marius> (yes I do send the desired command as an Marius> argument...e.g. "/bin/ls /home/someusr/dir > Marius> /home/

Runtime.exec ()

Hi there, I am having trouble getting Runtime.exec () to do anything (yes I do send the desired command as an argument...e.g. "/bin/ls /home/someusr/dir > /home/someusr/test"). I've tested my code on both a mkLinux (DR2.1u5) and Debian Linux machine running various flavors