
hoodlum7 at gmail
Aug 5, 2012, 5:22 PM
Post #5 of 12
(791 views)
Permalink
|
On Aug 5, 2012 1:28 PM, "Raymond Wagner" <raymond [at] wagnerrp> wrote: > > On 8/5/2012 16:11, Bill Meek wrote: >> >> On 08/05/2012 01:41 PM, Chris Porter wrote: >>> >>> I forgot to add, If I run the same command mythtv does on the linux >>> command >>> line it works just fine. >> >> >> Hi; >> >> Also, if you type: echo $? after your command line test, you'll >> see its exit code, although you'd expect any failure in the >> script to print a message. >> >> I'm not sure if: mythbackend --setverbose system will give you >> more information that the log you pasted in your 1st post, >> but it can't hurt (there's: --setloglevel debug too.) >> > > 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. > > _______________________________________________ > mythtv-users mailing list > mythtv-users [at] mythtv > http://www.mythtv.org/mailman/listinfo/mythtv-users 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.
|