--0016e647f02643f8b5046e50eb87
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Are you sure you are properly connecting to the server? Have you tried just
running something like ls and getting back a result? I just tried running a
simple script that sleeps for 100 seconds and it ran just fine after the
remote app was finished.

If that still leaves you in trouble - you might want to look into Screen
which is designed to run apps detached from the login shell so that would
certainly be of use if needed. This is the command I use to run an app
detached - screen -D -m command.rb

John


On Thu, Jul 9, 2009 at 6:34 PM, Enling Li <enling.li / loglogic.com> wrote:

> I tried that before. The thread won't solve the issue because once child
> thread established it does the same way as main tread. When the main
> thread terminates, the child gets killed also. It ends up nothing
> happened to the shell command.
>
> Thanks.
>
> Enling
>
> John W Higgins wrote:
> > On Thu, Jul 9, 2009 at 4:53 PM, Enling Li <enling.li / loglogic.com>
> > wrote:
> >
> >>
> > Would just dropping the ssh section into it's own thread accomplish your
> > task? That seems like a rather simple way of getting what you want.
> >
> > John
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

--0016e647f02643f8b5046e50eb87--