On 1/30/06, Chris Pinkham wrote: > No, his jobs actually ran, went to "stopping" and never made it out, the > backend stayed up the whole time. I've looked at his logs and can't tell > what is happening by looking at them, I do know though that the JobQueue > should > print out a success/fail message after the myth_system() call finishes, so it > appears that may not be finishing. The transition to JOB_STOPPING is just > about > the last thing that mythtranscode does before exitting, so I'm not 100% sure > that this is the case, but want to verify since I know the JobQueue should > also > be printing out something right after mythtranscode finishes but I don't see > this > in the logs. I've seen identical behaviour with the transcoder on occasion. It is very odd, since I don't really see anyway that JOB_STOPPING could be set and you get the 'Transcoding done' message without the application then immediately terminating. Yet I don't get a response from the jobqueue that the app terminated. Perhaps it would be useful to put a message right after the myth_system call to ensure it's not getting lost soemwehere after the return.
.Geoff _______________________________________________ mythtv-dev mailing list mythtv-dev@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev