🚀 go-pugleaf

> On Mon, 25 Jun 2001 20:00:44 +0200, Kristian wrote:
>
> > proc = Runtime.getRuntime().exec(new String[] {
> >     "tcsh", "-c", executableFile + " " + cfgFile + " >>&.logfile"});
> > // Contiously read the logfile in a separate thread
> > ....
> > // When finished, try to destroy the process:
> > proc.destroy();
> >
> > But the server process will not terminate...But this isn't a
> > surprise because the only process that terminates is the tcshell.
>
> You actually have terminated the process that you created with
> Runtime.exec().  You are starting "tcsh", and that is what you
> are killing.  But "tcsh" has created a subprocess, and that is
> the process that you want to be killed.
>
> You may be able to configure tcsh to kill its child processes when
> it is killed.

- Well if you could tell me of how to do that, this would be the easiest
solution for me. I have tried to give some options (flags) when starting
tcsh, But I didn't succeed...

Another thing that hit my mind is, if I configure tcsh, how would that
affect other processes that are launched from tcsh...or would the
configuration only consist my evironment that belongs to my Java
application?


>Or you could run the executable from the Java code.
> If you do that, you will have to capture the output in the Java code
> and write it to the log file.

- I know, but then I get some synchronization problems because I continously
read both from standard output and standard error. I know I can redirect
standard out and err to a logfile and will probably look for that solution
if the configuration of tcsh is  to prefer instead of the redirection

Regards
/Kristian