Sorry Ben, noted for next time. I haven't used dtruss or dtrace. But I'll
give that a shot.
Dean, What if you run kexec('ps')... do you actually see output in the
shell? I don't with Node v0.8 but with Node v0.4/v0.6 I do. I'm not sure
why there'd be a difference.
Thanks.
On Friday, July 20, 2012 7:41:25 PM UTC-5, Dean Mao wrote:
>
> It seems to work here... if I made it something like kexec("ls >
> testfile"), testfile actually has data in it. If you ran something like
> top, shouldn't it exit when node quits?
>
>
> On Fri, Jul 20, 2012 at 8:22 AM, JP Richardson <jprichard...@gmail.com>wrote:
>
>> Hi, I'm not sure if this is the right place to post this. I apologize in
>> advance if it's not.
>>
>> I'm trying to port my `kexec` module [
>> https://github.com/jprichardson/node-kexec] to Node v0.8. The problem is
>> that any of the `exec` family of functions from unistd.h don't seem to work
>> inside of a Node v0.8 add on. The calling process just terminates without
>> actually calling the process.
>>
>> Am I missing anything different in regard to Node v0.8 native addons?
>>
>> My binding.gyp file is pretty simple:
>>
>> {
>> 'targets': [
>> {
>> 'target_name': 'kexec',
>> 'sources': [ 'src/node_kexec.cpp' ]
>> }
>> ]
>> }
>>
>> Oh ya, I'm testing this on Mac OS X Lion. Any help would be appreciated.
>> Thanks!
>>
>> -JP
>>
>
>
