From: David Vallner Date: 2006-11-11T22:06:00+09:00 Subject: Re: Starting a system command and letting it be? --------------enigB3659C42E0039428074AD07E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Farrel Lifson wrote: > On 10/11/06, darenbell@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? >> >> >> >=20 > You could just use ruby threads? >=20 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 --------------enigB3659C42E0039428074AD07E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) iD8DBQFFVcrey6MhrS8astoRAlNUAJwKNQ8weyafMVtIJMwGUVKWO/Fp1ACcDUwO MIBCr2OZxP6lv2jSmzN7FRo= =Y5wj -----END PGP SIGNATURE----- --------------enigB3659C42E0039428074AD07E--