From: Jeremy Bopp <jeremy@...>
Date: 2010-10-23T00:33:09+09:00
Subject: Re: How to pass/return a string to calling program?

--------------enigDDECE5EDCD08EA941E2AF9C0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 10/22/2010 10:24 AM, Tony De wrote:
> Jeremy Bopp wrote in post #956216:
>> On 10/21/2010 06:12 PM, Tony De wrote:
>>>> These should definitely work.
>>>> they output something at all?  If they are printing something, try
>>> root@smi2-new:/usr/local/services/secure_dir# ./service_prov
>>> ../config_files/pms.2006.66056308205
>>> OKroot@smi2-new:/usr/local/services/secure_dir#
>>>
>>> I tried the sync option, but client didnt' get the response.  My perl=

>>> script does...
>>
>> Are you certain that your Ruby scripts are even running?  What is the
>> exit code your server gets back from running the scripts, and is that
>> result expected?  Do you have any way to independently confirm that yo=
ur
>> server is actually running your scripts?  If not, you might try
>> modifying one of your scripts to have it create an empty file in a wel=
l
>> known location which you could then check for existence after triggeri=
ng
>> your script to run.
>>
>> -Jeremy
>=20
> My script is running; I run it from the command line as I develop it. I=
=20
> can confirm that the script is doing everything it should.  It may be, =

> although I don't see how, an issue with the daemon calling the script. =

> I'll have to dig from the other direction.  I may be missing=20
> something...

I'm not sure you understood what I was asking.  Can you confirm that the
daemon is successfully executing your script?  Your script may work when
you run it yourself, but your daemon may not be running it at all for
one reason or another.  What you need to have is a way to verify that
your script ran otherwise successfully when invoked by your daemon proces=
s.

Given that your Perl scripts work as you expect, it's likely that due to
a configuration problem somewhere your Ruby scripts are never running
when the daemon tries to start them.  Maybe ruby is not in your PATH, or
perhaps your daemon is trying to invoke the scripts differently than you
do on the command line.

-Jeremy


--------------enigDDECE5EDCD08EA941E2AF9C0
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.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzBrq8ACgkQHt4KKRq6ZjfqXgCfdwp0Nc/g+FhAxWY+wGyU0ygn
Ai4An3gLDogHDt1j3q89Npdsl+NAw8kN
=IdiK
-----END PGP SIGNATURE-----

--------------enigDDECE5EDCD08EA941E2AF9C0--