From: "darenbell@..." <darenbell@...>
Date: 2006-11-13T22:55:04+09:00
Subject: Re: Starting a system command and letting it be?

Sorry for not responding sooner, but I was out of my office since my
last response.  David's solution worked perfectly.  Thanks for the help
everyone.

On Nov 11, 7:06 am, David Vallner <d...@vallner.net> wrote:
> Farrel Lifson wrote:
> > On 10/11/06, darenb...@gmail.com <darenb...@gmail.com> wrote:
> >> I'm writing a web service that accepts a call to initiate a few
> >> self-contained scripts on a RHEL4 webserver.  Being new to Ruby, I
> >> can't seem to find any documentation on how I could kick off the
> >> scripts without having the parent script wait on them to complete.
> >> Obviously, I don't need arguments our output back from the scripts, so
> >> all I'm concerned with is that they start and the parent can end
> >> without killing them.
>
> >> What's the best way to do this?
>
> > You could just use ruby threads?If the scripts do anything with standard input, they could hijack the
> Ruby script's from the thread. Use popen, or the open('|some-script')
> form instead of system?
> 
> David Vallner
> 
>  signature.asc
> 1KDownload