<p><br>
On Aug 5, 2012 1:28 PM, "Raymond Wagner" <<a href="mailto:raymond@wagnerrp.com">raymond@wagnerrp.com</a>> wrote:<br>
><br>
> On 8/5/2012 16:11, Bill Meek wrote:<br>
>><br>
>> On 08/05/2012 01:41 PM, Chris Porter wrote:<br>
>>><br>
>>> I forgot to add, If I run the same command mythtv does on the linux<br>
>>> command<br>
>>> line it works just fine.<br>
>><br>
>><br>
>> Hi;<br>
>><br>
>> Also, if you type: echo $? after your command line test, you'll<br>
>> see its exit code, although you'd expect any failure in the<br>
>> script to print a message.<br>
>><br>
>> I'm not sure if: mythbackend --setverbose system will give you<br>
>> more information that the log you pasted in your 1st post,<br>
>> but it can't hurt (there's: --setloglevel debug too.)<br>
>><br>
><br>
> The library for external system calls does not currently log output from external scripts. The scripts themselves are expected to handle all logging internally, and MythTV discards any stdout/stderr to /dev/null.<br>
><br>
> _______________________________________________<br>
> mythtv-users mailing list<br>
> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
> <a href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a></p>
<p>What has me banging my head against the wall is the script ruins outside mythtv's job queue, but not if it is run by the job queue.</p>