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

Enling,

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

> John,
>
> The key is I don't want to wait for the remote to finish. If I wait for
> remote to complete, I don't have problem.
>

Sorry I used the wrong wording - I meant that Machine A connected to Machine
B using Net::SSH and ran a script that slept for 100 seconds. Machine A then
disconnected without blocking and Machine B continued to execute the script
that was sleeping away. Again make sure you are connecting because you could
easily be not getting to the server at all - the block could just as easily
be a connection block and not an execution block. And if you are connecting
and still for some reason blocking - Screen is definitely the answer because
that is exactly what is it designed for.

John



> Thanks.
>
> Enling
>
>
> John W Higgins wrote:
> > 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
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

--0016e64eabf4b85051046e523490--