[mythtv-users] 0.25 lookup metadata as part of jobqueue?
Scott & Nicole Harris
snharris99 at live.com
Thu Mar 15 23:09:26 UTC 2012
>> I should also note that this is 0.24, not 0.25. I am unable to use 0.25
>> currently, because I am affected by ticket #10414, which is so bad for me
>> that if I try to start a recording over two, it will cause the currently
>> running recordings to stop.
>Ah, OK. Using --logfile is correct with 0.24. However, 0.24 doesn't
>pass logging options through to child processes. I don't know of any
>way to get 0.24 to actually tell mythtranscode to log messages when it's
>called from the backend. When you change the script (make a copy of the
>original before editing it) to start mythjobqueue, instead, and to use
>--logfile /var/log/mythtv/mythjobqueue.log do you get mythjobqueue
>logs? I'm guessing they--like mythbackend logs--wouldn't show much more
>than start/stop, but since the transcode is failing under mythjobqueue,
>seeing the failure might give us enough information to find out why
>mythtranscode is failing. If not, you may need to try just running
>mythtranscode to see if it fails, and why.
OK, just to make sure I understand. I can start mythjobqueue with --logfile
/var/log/mythtv/mythjobqueue.log. That should give me logging for what
mythjobqueue is doing? I have a bunch of recordings going tonight that I'll
be transcoding so if that's correct, I'll shutdown mythbackend and fire up
mythjobqueue and see what I get for you guys.
More information about the mythtv-users