Thanks for the reply!
setDaemon(true) makes the thread die when the program is closed. I want the
opposite effect.
I think the program I start on the remote server dies when I close the java app
because the channel object might be thrashed by the Java VM on exit.
Is there a way to send an exec ((ChannelExec)channel).setCommand(commandToRun);
in the background somehow? Or a way to send a command to a shell type of
channel [like in: session.openChannel("shell")] without System.in ? Maybe that
way it's not gonna die when I close my Java App.
Thank you for all your help.
Mike
> Date: Tue, 17 Jun 2008 13:23:34 +0100
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: [email protected]
> Subject: Re: [JSch-users] Channel Exec .setCommand(command) dies on program
> exit
>
>
> > When I close my java GUI, the process I run on Unix (with the unix nohup
> > command so it keeps running even if the session closes) dies after a few
> > seconds.
> >
> > Does anyone have any idea why?
>
> Look up java daemon threads
> and try
> setDaemon(true); on your worker thread.
>
> --
> M
>
_________________________________________________________________
Try Chicktionary, a game that tests how many words you can form from the
letters given. Find this and more puzzles at Live Search Games!
http://g.msn.ca/ca55/207-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users
